0

I thought adding urls to ones permissions in the manifest.json acted the same a the matches in content scripts, preventing the background page from running on any other websites. This question informed me that is not the case and this question claims that permissions allows the background page to interact with page code, what does that mean? I don't understand the point of urls in permissions

Community
  • 1
  • 1
WobbaFetttttt
  • 53
  • 2
  • 8
  • 3
    Various chrome.* API available in the background page can perform actions only on the permitted URLs. As for the first answer, it tells you what's already explained in the [architecture overview](https://developer.chrome.com/extensions/overview#arch). I'm not sure what to add to the overview, it's already simple. As for the 2nd answer, ignore the `code` part which is the wrong term. – wOxxOm Mar 04 '17 at 21:35
  • You appear to have assumed that the only way that one should be interacting with a URL is to inject a content script with a `content_scripts` directive in your *manifest.json*. That is limited thinking. There are may other ways to interact with pages, or other things for which you want access to specific URLs. – Makyen Mar 05 '17 at 03:08
  • like doing AJAX without cross-domain issues. – Zig Mandel Mar 05 '17 at 05:46

0 Answers0