Chrome extensions content scripts live in isolated worlds, meaning they share DOM, but have separate JavaScript sandboxes. Read more here:http://code.google.com/chrome/extensions/content_scripts.html#execution-environment
The workaround to this is to inject a
<script>
into the DOM of the page, but that code won't have privileges to call any chrome.*
APIs.
No comments:
Post a Comment