[
https://issues.apache.org/jira/browse/WOOKIE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247312#comment-13247312
]
Scott Wilson commented on WOOKIE-308:
-------------------------------------
This is a really painful one to try to implement, and I'm not really sure if
this has a real-world use. There is a W3C test case for this, where you have a
child iframe and it needs to get a storage event from the parent window, so it
also needs to be able to have access to window.widget.
I've tried client-side approaches (e.g. attaching event handlers to call
"window.widget = parent.widget" in frames as they load). Doesn't work - partly
as the test case is also triggered on the Load event too so there is a race.
The only way to ensure the iframe has a widget object before onLoad() is to
inject the script on the server. Which means a lot of parsing of the widget
package to figure out where to inject it.
Maybe the easiest answer to this is to just ignore it until we come across a UC
that really, really needs it. 99% conformance isn't bad :)
> Widget object unavailable in frames and iframes included in widget package
> --------------------------------------------------------------------------
>
> Key: WOOKIE-308
> URL: https://issues.apache.org/jira/browse/WOOKIE-308
> Project: Wookie
> Issue Type: Bug
> Components: Server
> Reporter: Scott Wilson
> Fix For: 0.10.0
>
>
> According to the W3C Widget API spec, the widget javascript object needs to
> be available to all documents using the widget origin, and that includes
> frames and iframes as well as the start page. Currently we only inject the
> scripts into the start page.
> To conform 100% we need to implement this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
