I can think of two possibilities.<br><br>One would be to allow the param element as a child of any element (or any block level element?)<br><a href="http://www.whatwg.org/specs/web-apps/current-work/#param">http://www.whatwg.org/specs/web-apps/current-work/#param
</a><br><br>And then make an attribute of HTMLElement called params<br> readonly attribute HTMLCollection params;<br><br>Where params is a collection of HTMLParamElements that are children (not further descendants) of that element.
<br><br>That would make this:<br><div id="foo"><param name="answer" value="42">Some more content</div><br><br>easy to access via JavaScript:<br>var foo = document.getElementById
("foo");<br>if(foo.params['answer'] == 42) {<br> // it is!!<br>}<br><br>The only other possibility I can think of would be an HTML attribute called "params" that would be a list of tokenized name value pairs, but that sounds even hairier to implement.
<br><br>This would have simplified something I did last week involving the Google Maps API, where I did, as mentioned, make up a fake attribute. There may be better ways to do this. <br><br><div><span class="gmail_quote">
On 4/9/07, <b class="gmail_sendername">ddailey</b> <<a href="mailto:ddailey@zoominternet.net">ddailey@zoominternet.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Henri, thanks for the link to PPK's suggestions -- I rather like many of<br>them.<br><br>Henri Sivonen wrote:<br><br>> At <a href="http://www.quirksmode.org/blog/archives/2007/04/html_5.html">http://www.quirksmode.org/blog/archives/2007/04/html_5.html
</a> PPK<br>> suggests having an attribute for storing private data for scripts.<br>><br><br>I'm having a hard time seeing what you're talking about here. When PPK says<br>"This attribute [to store data for unobtrusive scripts] should be valid for
<br>all HTML elements. " I'm rather sure I've lost you.<br><br>Sometimes, I'll stick a long string inside an invisible textarea just so as<br>to give JavaScript something to chew on -- then I can use string.split
to<br>pull the data apart. Is that what you mean? I rather doubt it.<br><br>By "private" you don't really mean inaccessible to end users do you?<br><br>I think I need an example to understand.<br><br>regards,
<br>David<br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Jon Barnett