Don't you understand that the need to speak before our mozilla king to be heard is already a problem, no matter how benevolent the king is we still become supplicants before him. And not everyone will be willing to ask, so things die silently.

And then there also is the issue that mozilla has limited resources. So even if you wanted to help you can't help everyone.

This does not exist in the old extension ecosystem or in regular software development. You don't have to beg anyone to please spend time a particular usecase.

It may be painful to get things working yourself, but at least it's an option you have.

Here's an example of users helping each other without needing to petition for support from orbital HQ: http://stackoverflow.com/questions/36927096/firefox-command-...

Will the WebExtensions API be powerful enough to write a "browser firewall"? Essentially give users automatic/manual control over about every process run by the browser.

I don't think we're exposing native process semantics to WebExtensions, but the webRequest API can intercept and modify any request initiated by web content.

If this use case is important to you, please file a bug explaining your needs and/or fill out the survey at https://wiki.mozilla.org/Add-ons/Contribute#Improve_add-ons_....