Manifest v3 Update
>Google has introduced declarativeNetRequest (DNR) to replace the blocking webRequest API.<p>...<p>>After discussing this with several content blocking extension developers, we have decided to implement DNR and continue maintaining support for blocking webRequest.<p>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.<p>>We will support blocking webRequest until there’s a better solution which covers all use cases <i>we consider important</i> ... (emphasis mine)<p>And there it is.<p>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).<p>That's my cynical, entirely pessimistic outlook of it all anyway.<p>I'd like to read Raymond Hill's thoughts on this.