One thing we've considered is having extension declare some of their URLs "public," which would let web content navigate to or iframe those URLs.
There's some security benefit in not letting arbitrary render processes access the chrome.* APIs. Another possibility is to have a "content page" that is like a content script in that it gets a message-passing channel back to the main extension process, but has a URL and HTML. (We'd have to think about what kind of URL it would have.) Adam On Mon, Nov 30, 2009 at 8:34 AM, Aaron Boodman <[email protected]> wrote: > +abarth, security guru > > This is by design. I think it is something we may eventually > reconsider, but we started this way to be conservative. > > - a > > On Mon, Nov 30, 2009 at 1:17 AM, Arrix <[email protected]> wrote: >> Hello, >> >> I'm trying to embed an extension page (chrome-extension://<id>/ >> somepage.html) as an iframe inside the content page. It seems that the >> extension page cannot access any chrome APIs. >> console.log(chrome.extension) //=> undefined >> >> The extension page works well when loaded in a tab. >> Is this a designed behavior or an implementation limitation? >> >> Anyhow, is this usage (extension page in iframe of content pages) >> discouraged for some reason? >> The use case is to show a context popup in a webpage. iframe is used >> to avoid css conflicts. >> >> >> Thanks, >> Arrix >> >> -- >> >> 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. >> >> >> > -- 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.
