Forum Discussion

zmni's avatar
zmni
Brass Contributor
May 30, 2019

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 remov...
cbomtempo's avatar
cbomtempo
Iron Contributor
May 30, 2019

zmni Edge will be a Chromium based browser, so it's better to expect every engine change to reflect on Edge as well. I guess there's no way that Microsoft would fork away from Chromium.

zmni's avatar
zmni
Brass Contributor
May 31, 2019

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.

  • cbomtempo's avatar
    cbomtempo
    Iron Contributor
    May 31, 2019

    zmni I agree with you, but that's a core feature that if Microsoft move to a different direction than Chrome would break the extensions compatibility. But on the other hand it could make users switch to Edge because it would have "better" extensions. ¯\_(ツ)_/¯

Resources