+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.
