Content blocking: We have no immediate plans to remove
blocking webRequest and are working with add-on developers to gain a better understanding of how they use the APIs in question to help determine how to best support them.
Please be advised that the statement may be received as a bit milquetoast even if that is not the intent; I believe that a published roadmap for
blocking webRequest would do much to inspire developer confidence. In my case, I have a plugin that does NSFW image moderation fully client side and so it doesn’t follow the usual ad blocking use case that has garnered public attention - and perhaps the protection, as it were, that that attention might help ad blocking use cases attract. However, I believe Mozilla wishes to take the high road on this, and to me the thing that separates statements of commitment from merely gladhanding or appeasement is a clear roadmap. In my mind, a roadmap is the perfect foil to something embroiled in controversy like this, as it embodies the whole, well-formed dream that Mozilla has around the feature set - Chrome or not! - and speaks to the future we wish to see and build.
Does such a roadmap exist? If not, would Mozilla please be willing to create and publish one? From the existence of the API extensions already in place e.g.
filterResponseData my hope is that Mozilla has a clear, strong internal vision of this and as a part of your community I’m wondering if we can get a peek at it.
Thanks for making the browser that makes my plugin possible!