Forum Discussion
Manifest V3: Web Request Changes
So, Google plan to introduce manifest v3 that limit extensions blocking capability by removing webRequest API and replacing it with super limited declarativeNetRequest.
Please, please don't remove/change/limit this API. If microsoft truly listen to it's user and many extensions developer complaining this changes.
I have good faith microsoft will listen, this is also good opportunity for microsoft, more user for their new chromium based browser.
Related discussions:
- https://bugs.chromium.org/p/chromium/issues/detail?id=896897
- https://groups.google.com/a/chromium.org/forum/#!topic/chromium-extensions/veJy9uAwS00
- https://github.com/uBlockOrigin/uBlock-issues/issues/338
- https://news.ycombinator.com/item?id=20044430
- All reddit threads (to many can't list here).
39 Replies
Agreed. As much as I like Edge and Chromium Edge, without uBlock or something similar, I'd have to switch over to Firefox. zmni
This recent digging in of Google in regards to Manifest V3 has me equally concerned.
I switched from Firefox to Edge Insider and absolutely love it, but if I an expect to lose functionality in the future I might as well switch back.
Everyone is saying since this will be baked into Chromium you can expect it to roll out to everyone unless there is a distinct fork which increases work to implement new versions. I'd assume with Microsoft switching to Chromium Edge to remove the need to maintain the codebase they'd be unlikely to want to do the same. If I was a manager I'd begrudgingly accept the Manifest V3 changes into my product as the value to cost of losing some power users would likely be much less a hit than the increased workload on my developers.
I strongly agree with this. If the Manifest V3 change also comes to Chromium Edge and kills the functions that allow for add-ons like Ublock Origin then its a non starter for me. Which would be sad because I have been impressed so far with the new Edge (still kinda ugly like chrome and missing important features, but hopeful)
cbomtempo If they are capable of https://www.theverge.com/2019/4/8/18300772/ stuff from chromium and adding https://www.microsoftedgeinsider.com/en-us/whats-new to Edge, I am sure it is very easy for them to create set of patches to skip/undo this API changes. The problem is whether they really want to do it or not.
I hope the Msedge team can convey an official statement about this.
