Hi Adam, Thanks for the details. I'm confused by the bug description, I think this problem may have been misdiagnosed. I'm pretty sure what I'm seeing is a regression. Accessing contentWindow used to be possible in Windows Chromium builds, but I see that it is now broken there too. It still works in the latest Windows beta build. Perhaps this is just a timing issue(?), but if not, then since it used to work, it's a surprise to me that it would require large changes to fix a regression, although of course I understand that this could be the state. In any case, it's a pretty significant limitation to not be able to use postMessage from a content script to post to an iframe...hope you guys can get this remedied soon.
Thanks! On Dec 23, 3:36 pm, Adam Barth <[email protected]> wrote: > This is the bug:http://code.google.com/p/chromium/issues/detail?id=20773 > > It's unlikely to get fixed in Mstone-4 because it requires large > changes to how the lifetime of these objects is managed. It should > make it for Mstone-5 though. > > Adam > > > > On Wed, Dec 23, 2009 at 3:18 PM, donaddon <[email protected]> wrote: > > 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 > > 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.
