Please find below the cause for your specific issue and the cause for not getting the details of failure in the console log. Before Chrome 93, the service worker file must be in the root path where manifest.json is. This is a limitation of Service Worker specification, relaxed for extensions since Chrome 93. If, for … Read more
One thing that is important to know is that Content Scripts share the same DOM as the current page, but they don’t share access to variables. The best way of dealing with this case is, from the content script, to inject a script tag into the current DOM that will read the variables in the … Read more
You cannot run code on a site without the appropriate permissions. Fortunately, you can add the host permissions to optional_permissions in the manifest file to declare them optional and still allow the extension to use them. In response to a user gesture, you can use chrome.permission.request to request additional permissions. This API can only be … Read more
I achieved capturing all HTTP requests and responses made by a website, by injecting a script to DOM. I injected injected.js to DOM using following script: /** * code in inject.js * added “web_accessible_resources”: [“injected.js”] to manifest.json */ var s = document.createElement(‘script’); s.src = chrome.extension.getURL(‘injected.js’); s.onload = function() { this.remove(); }; (document.head || document.documentElement).appendChild(s); This … Read more
According to the official docs you should use postMessage in the sender and message event listener in the receiver. Here is an example: Your website’s page.html var data = { type: “FROM_PAGE”, text: “Hello from the webpage!” }; window.postMessage(data, “*”); Content script: (injected using chrome.tabs.executeScript(tabid, {code:…) window.addEventListener(“message”, function(event) { // We only accept messages from … Read more
.xpi file format (Extension Packaging) The .xpi files that are used as containers for Mozilla (Firefox, Thunderbird, etc.) extensions are merely zip archives that have had the file extension changed to .xpi with the files added to the archive using either “deflate” compression, or uncompressed. If you use any other type of compression, other than … Read more
In general, you cannot change the response body of a HTTP request using the standard Chrome extension APIs. This feature is being requested at 104058: WebRequest API: allow extension to edit response body. Star the issue to get notified of updates. If you want to edit the response body for a known XMLHttpRequest, inject code … Read more
The inability to insert an external iframe in Chrome is a bug (crbug.com/408932). If you want to embed an external frame in an external website, then it must be loaded in a frame that is packaged with your extension. manifest.json { “name”: “Embed external site”, “version”: “1”, “manifest_version”: 2, “content_scripts”: [{ “js”: [“contentscript.js”], “matches”: [“*://*/*”], … Read more
It’s possible, but you have to be careful. Trying to require() a package means that node will try to locate its files in your file system. A chrome extension only has access to the files you declare in the manifest, not your filesystem. To get around this, use a module bundler like Webpack, which will … Read more
The most likely cause of failure is the activation of the default Content security policy when “manifest_version”: 2 is active. A consequence of the default CSP is that inline JavaScript will not be executed. <script>chrome.extension.onConnect.addListener(…);</script> The previous line is an example of inline code. The solution is to place the script in an external JS … Read more