4 ms·
Microsoft don't really invest the right kind of resources into Edge to make that happen. There are sound technical reasons (aside from the obvious financial rea
by chippiewill 2y ago
Microsoft don't really invest the right kind of resources into Edge to make that happen. There are sound technical reasons (aside from the obvious financial reason) why Google wants to make this change, I suspect this'll unblock the Chromium team making a very substantial refactor of the networking layer which Microsoft can't feasibly maintain a fork of.
- harrygeez 2y agoI wish all Chromium forks would band together to maintain a base that supports Manifest V2, it shouldn't be that difficult to each chip in some funding.
- wavemode 2y ago> I suspect this'll unblock the Chromium team making a very substantial refactor of the networking layer I'm curious as to why you suspect this. Have they stated so?
- chippiewill 2y agoThe webRequestBlocking API exposes fairly low level hooks into the networking stack to the javascript layer which would be a significant limitation to performance optimisation in how requests are processed. That said I've now read that the API is still available to policy based extensions (essentially OS installed extensions) in manifest v3, so that doesn't hold water since it's literally the same API.