I'm not sure I quite follow what issue you're running into, but currently content scripts can't see inside iframes. That's a bug that I haven't gotten around to fixing yet. I hope to spend some more time on these issues in the coming weeks
As a workaround in the meantime, you can try setting the HTMLFrameElement's src property to a JavaScript URL. Adam On Thu, Sep 3, 2009 at 11:45 AM, Daniel Wagner-Hall<[email protected]> wrote: > > Hi, > > I'm currently executing javascript in pages from a content script by > injecting a script tag into the document, firing a DOM event when it's > done to know when it's done, and return strings, to get around > sandboxing. > > This is working fine in general, but breaks for iframes. > Specifically, I'm trying to inject a script tag into the iframe which > has no src. If I do this in an ordinary page with javascript in, > rather than from a content script, the event fires just fine. If I > inject the script into the whole page from the content script, rather > than into the iframe, the event fires fine. But if I inject it in to > the iframe, the event is not seen by the listener in the content > script. > > Is this an intentional part of the sandbox, or has something which > should be able to get through accidentally not (warranting a bug > report)? > > Thanks (and sorry for being so horribly edge casey once again!) > > Daniel > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
