Manifest v3 Update
>Google has introduced declarativeNetRequest (DNR) to replace the blocking webRequest API....>After discussing this with several content blocking extension developers, we have decided to implement DNR and continue maintaining support for blocking webRequest.We've seen this before -- a number of times. This is what's put forth to avoid a cacophony and push back from developers and end-users alike. Both technologies will be supported for a short time before blocking webRequest is taken out altogether at a relatively short time thereafter.>We will support blocking webRequest until there’s a better solution which covers all use cases we consider important ... (emphasis mine)And there it is.In a short time we'll read a statement -- released on a Friday afternoon -- stating the EOL for blocking webRequest with little-to-nothing in the way of analogous behavior because it wasn't considered important by Mozilla (or, perhaps, the pressure from Google was too much).That's my cynical, entirely pessimistic outlook of it all anyway.I'd like to read Raymond Hill's thoughts on this.