I am in the process of converting my manifest two chrome extension to manifest 3. I am proceeding nicely, except for one item that is driving me crazy. That item is a hot reload of the service worker during debugging. I am currently reloading the extension, which is painful for debugging. I have read that setting up a hot reload in the manifest is possible. I have tried several entries in the manifest file, but none had any effect. Could somebody point me in the correct direction? It seems like there is conflicting information all over the web. A sample of a manifest would be greatly appreciated.
Thanks,
Tom
Related
Upon switching to Chrome's Manifest 3 format (and per its requirements, using a service worker if that's somehow relevant), my options page shows up like this:
Only upon moving away from the tab and reentering it, do I get my options to show up:
It doesn't matter if I trigger the options page via the toolbar or via its extensions entry.
I do have the options page in the manifest file, so I wouldn't think the change to a service worker has relevance. I don't have any listeners for the page visibility API.
Even when I blank out my options code with a minimum of content and update the unpacked extension, I still experience this behavior.
Any configuration or behaviors that could be triggering this (and how to overcome)?
It seems that whatever the cause of this behavior, that it only occurs when loading an unpacked extension. When I use web-ext to build a zip file and open that in Chrome, I don't see this problem.
Not ideal, but a bug I can at least live with.
I have switched to using Content-Security-Policy for my website. I'm starting to see reports about the following not being allowed: https://www.pagespeed-mod.com/v1/taas
Does anyone know why the website is trying to load this file? I'm using Google Analytics and Tag Manager, but I don't think that I have any page speed mod installed. Maybe this is an extension in the user's browser? Or when they open developer tools? Another source I could think of is automatic optimization through Cloudflare which I'm also running on.
Extra info: The source of loading this script is https://3001.scriptcdn.net/code/static/1 which doesn't reveal much about who made that.
Had the exactly the same issue and preventing me from using Element Inspector/ debugger. It appears to be some Chrome extension you have installed gone rogue, see if you have extension called "Auto Refresh Plus" installed like i did before.
I also see reports on https://www.pagespeed-mod.com/v1/taas being blocked with the same source of loading. It seems to happen in short periods on the various resources I have reports from. This indicates that it is related to the user/browser and not related to the site itself.
The same can be seen with translators, extensions, security proxies etc. I have given up trying to attribute the source of anything that is likely not caused by legitimate site content.
Our Chrome Extension was removed from the Google Chrome store (and Google Marketplace) and we didn't get any notification before hand that it was going to be removed, and didn't get notified that it was removed (or for what reason).
Our extension is FollowUp.cc (a growing company that depends on the extension)
One of our engineers started reverting changes and republished an older version of the extension in hopes that that may help. We're out of ideas.
Any help would be appreciated!
I have an extension in the Chrome Webstore with ~400 000 users. Since a couple of months ago I have been getting e-mails from users whose extension has stopped working for them. They're basically just seeing the HTML page in the popup and options page. No content dynamically added by any JavaScript. After some helpful debugging from one user it appeared that the JavaScript files were gone. He sent me the following screenshot:
So what appears to happen is that the JS files become unreachable, or disappear. My guess is that this happen when an upgrade occurs. I haven't moved or changed the names of any files in any recent updates. No big changes have occurred at all.
I have solved this by sending instructions on how to find the extension on the hard drive, and attaching the extension files, so they manually themselves have to patch the extension. This always works. Now today, after receiving 4 e-mails within an hour with the same problem, I've had enough.
One user had all her extensions stop working at the same time. My guess being that this problem was the culprit. Me sending the patch to her solved the issue for my extension at least.
So my question to stackoverflow is: Has anyone else experienced this? This seems like quite a serious issue with Chrome. It started appearing around Chrome 20 and still happens with 22. My manifest version was prior to a couple of days ago 1.
The extension in question: http://chrome.google.com/webstore/detail/pnjaodmkngahhkoihejjehlcdlnohgmp?hl=en.
I have a popular Chrome extension that is being targeted by a specific site and they are messing with our extensions functionality and telling visitors to uninstall our extension. They are detecting we are running in the browser by checking for our manifest file via looking for the URL chrome-extension://our-app-id/manifest.json. Is there anyway I can prevent this?
I tried using content-security-policy but that seems to only help with cross-scripting. If not seems like a security hole on google's part; I don't want sites knowing what extensions I am running in my browser.
Manifest version 2 that is tentatively scheduled for version 18 should fix this.
[...] today, all the resources inside your extension (e.g., images)
are visible to web pages. We're changing the default to "not visible"
and then adding a manifest attribute to let you whitelist the
resources that you want to be accessible to web pages.