On Sep 9, 1:28 pm, Aaron Boodman <[email protected]> wrote:
> None of the extension APIs are supported from content scripts. The
> only thing content scripts can do is access the DOM of the page and
> communicate to their parent extension (toolstrips, background pages,
> etc).
>
> This is a confusion a few people have had, which makes me think this
> part of our introductory documentation is not clear.
>
> In this case, what you need to do is use content script messaging
> (http://chromeextensionsdocs.appspot.com/content_scripts.html#messaging)
> to communicate to an extension page (probably a background page
> (http://chromeextensionsdocs.appspot.com/background_pages.html)),
> which can call the APIs.
>
> - a
thx for the clarification -- got things working
I also tried host page communication (http://
chromeextensionsdocs.appspot.com/content_scripts.html#host-page-
communication), both
host page -> content script -> toolstrip, which worked fine
and
toolstrip -> content script -> host page, which I could not get
working. Furthermore, adding the event listener in my host page to
receive the messages seemed to block a timer function set up with
setInterval.
Should I put together an example / log a bug? Not sure if you want the
general public logging issues (or if we even can).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
