I haven't been able to find this bug, Adam can you give me a bug number? This is very serious for us, as it is extremely difficult to do cross-frame messaging from a content script without it.
On Dec 17, 1:02 am, Adam Barth <[email protected]> wrote: > This is a known bug. It's on my plate for post-Mstone-4. > > Adam > > On Wed, Dec 16, 2009 at 3:04 PM, donaddon <[email protected]> wrote: > > We have been using HTML5's postmessage for cross-frame communication > > from our content script, but in recent builds on Mac & Linux (no > > problem on Windows), the following always returns undefined from our > > content script: > > > window.frames[0] -or- document.getElementById > > ("theFrame").contentWindow > > > (this is regardless of all_frames). Is this expected or known? > > Suggestions on a workaround? > > > I suppose for a workaround we can go to content script communication, > > but that's a few more steps: DOM->content script->other window content > > script -> other DOM > > > -- > > > 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 > > athttp://groups.google.com/group/chromium-extensions?hl=en. -- 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.
