Repro created, bug submitted here: http://code.google.com/p/chromium/issues/detail?id=29155
Only workaround I've come up with so far is to poll for variable changes so I can do my work in a context where window.parent is available (setTimeout didn't change the context). On Dec 1, 4:10 pm, donaddon <[email protected]> wrote: > Okay, I'll work on a repro. It's really odd, because it's not just a > script isolation issue. I can set other window variables like > window.customVar, and access that later in the same web page, it's > just a problem with window.top & window.parent, like it's a cross- > frame security context issue, not an isolation issue. > > On Dec 1, 3:45 pm, Adam Barth <[email protected]> wrote: > > > On Tue, Dec 1, 2009 at 3:36 PM, donaddon <[email protected]> wrote: > > > I have script running in a web page, listening for a custom DOM event > > > raised by a content script. It's running in an iframe, but again, > > > it's not a content script, it's in-page script. > > > > For some reason, when the event handler code in the web page executes, > > > that script cannot cannot see window.top or window.parent, they are > > > undefined. I've seen discussions about accessing window.top from > > > content script, but this is not a content script -- it's web page > > > script being invoked by an event raised by a content script. > > > > Is this expected, or a known bug, or do I need to isolate & repro? > > > You're right that the content script issue is a known bug, but I > > haven't heard for the same problem outside of a content script. If > > you could isolate and repro, that would be helpful. > > > Thanks, > > Adam -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
