I mean that you should be able to use the HTML5 postMessage API to communicate between your extension and the iframe:
http://ajaxian.com/archives/using-html-5-postmessage Adam On Thu, Sep 24, 2009 at 4:58 PM, Michael Weber <[email protected]> wrote: > > do you mean > > 1) That the network page, hosted in the mole's iframe, should be able > to use chrome.extension.onConnect.addListener / > port.onMessage.addListener to receive messages from the mole and then > use chrome.extension.connect / postMessage to send messages to the > mole, with the mole using the same apis? Just tried that and do not > have it working. > > or, > 2) That the network page should work with a content script. But > content script ports are accessed via the tabs api, and there is not > tab associated with the network page in my mole's iframe... > > or > 3) something that I am completely missing. > > cheers > Michael > > On Sep 24, 3:28 pm, Adam Barth <[email protected]> wrote: >> You should be able to communicate with the iframe using postMessage. >> We don't allow direct DOM access to prevent the network page from >> hacking the extension. >> >> Adam >> >> On Thu, Sep 24, 2009 at 12:47 PM, Michael Weber >> >> >> >> <[email protected]> wrote: >> >> > Well duh guess is makes sense that document.domain doesn't help since >> > the two docs do not original from the same host -- this is not a "two >> > subdomains" problem. >> >> > Anyway, given that the mole has control over what document it loads, >> > it would be great to enable JavaScript permissions into that loaded >> > document. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
