3 ms·
Both things are under the "manifest v3" umbrella. He was complaining about the deprecation of the blocking version of chrome.webRequest The change described h
by tyingq 5y ago
Both things are under the "manifest v3" umbrella. He was complaining about the deprecation of the blocking version of chrome.webRequest
The change described here is something else under the same umbrella. Not the change he was talking about. But generally, the whole of "manifest v3" will render lots of useful extensions dead in the water. Any heuristic ad blockers, things like tampermonkey, etc. If you want things like that, you'll have to move to Firefox.
- ROARosen 5y agoI understand he was referring to a different API than the one discussed. My question is if the API change he was referring to is still being implemented in Manifest v3 (I've edited my comment accordingly).
- deleted 5y ago[deleted]
- tyingq 5y agoI don't think Google has said when extensions with Manifest V2 will no longer work. And, technically, you can still use the blocking webrequest in a Manifest V3 extension, if the extension is "force installed". I think they are waiting for the hoopla to die down a bit before they close the door hard.
- ece 5y agoIt seems like Firefox will support Manifest v3 in a way that doesn't break compatibility with other browsers and support the blocking webRequest API as well: https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/ https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...