- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 10 Jul 2008 13:03:28 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5846 Hallvord R. M. Steen <hallvord@opera.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NEEDSINFO | --- Comment #2 from Hallvord R. M. Steen <hallvord@opera.com> 2008-07-10 13:03:27 --- > What's the use case? Simplifies passing data to a script inside an embedded SVG graphic or other embedded document. > Would this also apply to HTML content? I see no reason to limit it to SVG. Scripts in any type of document embedded by an OBJECT might be interested in the PARAM tags of that object. > Would it apply cross-site? Yes. That is one of the important use cases, because it is the one we can't work around now (scripts in child documents from the same origin could always investigate the DOM of their parent to find PARAMs) and indeed this use case was the reason the mailing list thread was started. > Why do query parameters not handle this? Query parameters is an alternative. However, there are limits to how much data you can pass in a URL, and it introduces unneccessary URLencoding/decoding requirements. Also, not adding this feature makes <PARAM> useless in cross-domain embedding scenarios. I think this seems like an oversight in the spec since the author's intention when specifying PARAMs presumably is to make those parameters available to the embedded content. We already have this working for plugins (also cross-domain) but we don't have it for natively supported content. Hixie, I hope this answers the questions so I revert the bug from NEEDSINFO state. Thanks for following up. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 10 July 2008 13:04:01 UTC