101–110 of 396 posts
Wait FF is copying this too?!?
Chrome is additionally planning to remove support for manifest V2 as well, Firefox can't start to do this because they don't support V3 in their store yet.
Earlier quoted context omitted.
You realize Firefox only exists because it serves Google's interests right? And while Brave might be based on Chromium, it is distinct; in addition to not crippling nativewebrequest as chrome will, it's native adblocker is compatible with the same lists as ublock origin. So I would go with Brave :)
What will Brave, Vivaldi, etc, do when Google makes some change that breaks the current APIs? Do they have the resources and are willing to continue to support them?
Earlier quoted context omitted.
I really hope so. Any good sources to find out Mozilla’s stance?
https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat... > We will support blocking webRequest until there’s a better solution which covers all use cases we consider important, since DNR as currently implemented by Chrome does not yet meet the needs of extension developers.
I honestly think that Google underestimated how much they are going to piss off users with MV3. There are thousands of extensions that will stop working and be impossible to build. But also there will be a lot of broken experiences as remote loading is forbidden and fixes will need a new release. Can't wait, but that's a very good opportunity for Firefox as Firefox will become more powerful than Chrome
In the article, Firefox is cited as intending to adopt MV3 for compatibility reasons. If they indeed do so, I'm not sure how much relief running Firefox will offer from the more evil aspects of MV3.
From that viewpoint, the new restrictions could actually be a good thing.
Earlier quoted context omitted.
Chrome allows you to disable installation of extensions via Group Policy for a looong time now: https://security.stackexchange.com/questions/66239/how-to-pr...
I'm just not smart enough to figure that out. That first answer references steps that don't exist on any Chromebook I've ever seen. So I assume I have to enroll the machine in a group policy externally? I have no idea. Never been able to figure it out. I usually just end up installing an extension (oh, the irony) that blocks the extensions domain. :/
That's because Group Policies are a Windows-only thing.
I honestly think that Google underestimated how much they are going to piss off users with MV3. There are thousands of extensions that will stop working and be impossible to build. But also there will be a lot of broken experiences as remote loading is forbidden and fixes will need a new release. Can't wait, but that's a very good opportunity for Firefox as Firefox will become more powerful than Chrome
In the article, Firefox is cited as intending to adopt MV3 for compatibility reasons. If they indeed do so, I'm not sure how much relief running Firefox will offer from the more evil aspects of MV3.
Mentioning again to the entrepreneurical ones here that I want to pay money for something that works like old Firefox but uses the new supposedly more secure code base. I pay for IntelliJ so why not pay for the just as important browser if I can get one that I like? Just don't increase the pricing to Jetbrains level until you have Jetbrains level features.
Does anyone know how the Manifest v3 changes will affect extensions that modify pages for accessibility reasons?
Previously extensions could be background pages, with access to DOM & Web Platform apis. MV3 currently reduces them to Service Workers, able to use far far far less capabilities. This is a massive massive downgrade for Extensions, unfathomable really. A Mozillaian proposed a less limited Limited Events Page but Google has snubbed it & not discussed. https://github.com/w3c/webextensions/issues/134 Extensions are force…
I don't. Especially not with FloC[0][1].
[0]: https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-... [1]: https://developer.chrome.com/docs/privacy-sandbox/floc/
I honestly think that Google underestimated how much they are going to piss off users with MV3. There are thousands of extensions that will stop working and be impossible to build. But also there will be a lot of broken experiences as remote loading is forbidden and fixes will need a new release. Can't wait, but that's a very good opportunity for Firefox as Firefox will become more powerful than Chrome