mrflix
Cancellation of support in Chrome Web Store
Translation of the text in the red block: "This extension is no longer available because it does not meet guidelines."
I have been using your Chrome extension for 6 years now and have not found an alternative yet, as it was not required. I wanted to install your application separately from the Chrome web store in the browser. Is there any way to do this?
Chrome is requiring a new standard for web extensions (Manifest V3) and Dimensions is not compatible. I'm looking into making it compatible. For now you can use the extension Firefox, which doesn't require Manifest V3 yet.
Chrome is requiring a new standard for web extensions (Manifest V3) and Dimensions is not compatible. I'm looking into making it compatible. For now you can use the extension Firefox, which doesn't require Manifest V3 yet.
Try to find the problem in VS Code with Github Copilot and select Agent mode to get it fixed. Currently Github Copilot has a Free Plan.
Any updates on this? Dimensions is now fully discontinued by Chrome https://x.com/ArtemR/status/1943763658070536618.
Looks like @mrflix has a PR to push that will revive the extension https://github.com/mrflix/dimensions/pull/55. So it's coming back soon, hopefully 🤞.
Hopefully the fix is on the way used this for so many years over many PC's, but i was using it earlier and then chrome/brave said there was malware in the Extensions and to uninstall it! 👀
Manifest v3 version is out and the extension is back on the Chrome store!
https://github.com/mrflix/dimensions/releases/tag/v3.0.0 https://chromewebstore.google.com/detail/dimensions/baocaagndhipibgklemoalmkljaimfdj
One thing of concern is in order to reactivate the extension, Chrome asked me if it should accept the permission to read data from all websites. Is this new less restrictive permission absolutely necessary @mrflix @xDhii?
Thank you for @archon810 for getting back to me on that. The new wider permissions where introduced with @xDhii's pull request. When I reviewed it I read into the newly added host_permissions attribute. I learned that it's needed to "Inject a content script programmatically". So far, the activeTab attribute was enough to give us that permission for the current page whenever the extension is triggered. Your comment prompted me to read into it again and turns out activeTab is still sufficient:
While the "activeTab" permission is enabled for a tab, an extension can:
- Call scripting.insertCSS() or scripting.executeScript() on that tab if the "scripting" permission is also declared (as in the example above).
Source: https://developer.chrome.com/docs/extensions/develop/concepts/activeTab
I just submitted version 3.0.1 for review with the host_permissions attribute removed.
Awesome, that's great @mrflix. Perhaps consider adding every release to https://github.com/mrflix/dimensions/releases too?