Does content_scripts matches “chrome-extension://*/*” work?

No. Only ftp:, file:, http: and https: can be matched by a content script declaration.

Invalid URL patterns at any of the matches and exclude_matches fields are rejected (generating an error when trying to load the extension).

Invalid patterns at the permissions option in the manifest file are ignored.

If you want to run a script on a tab from your extension, use chrome.extension.getViews in your background script.
Even better, design your extension’s pages such that they effectively communicate with each other (example).

Leave a Comment