Try to implement activeTab permissions for trust and speed about ghosttext-for-chrome HOT 5 CLOSED

I tried in a separate branch (b9d689d), I don't know what's up with this:

Why do you think this is happening?

from ghosttext-for-chrome.

I got the same error when setting using "activeTab". It seems that chrome handles the background.js in another way, where the background.js scripts acts as a part of the content script, when using this option. Since a HTTP server does net sends a asterisks CORS header by default this error is the same when doing an normal ajax request with another url not matching the site delivering URL.

Maybe a chrome bug or is the documentation here https://developer.chrome.com/extensions/activeTab is poor?

from ghosttext-for-chrome.

activeTab is not the issue, that permission is in the master branch and it works; chrome.tabs.executeScript is. I think it somehow messes something up, it does look like a bug. :(

from ghosttext-for-chrome.

Of course the bug was in my head. I didn't RTFM. The only problem was that the content script had the permission to access all sites, but executeScript required that permission anyway in the permissions parameter. So this fixed it

"permissions": [
    "activeTab", "http://localhost/"
],

from ghosttext-for-chrome.

Current permission screen:

from ghosttext-for-chrome.