News for hackers. Stuff that matters.
Re:Angular 1.x Banned from Firefox Addons by fuzzy2 on Friday October 21, 2016 @02:33AM (#12758555)
> By definition, browser extensions need to be able to access things such as page content.

On Firefox/XUL maybe. Web Extensions (like in Chrome) work much like Android apps: You need to acknowledge their desired permissions up front. They can’t request more later.

Of course you may need these permissions to create your extension.

Re:Angular 1.x Banned from Firefox Addons by y0ghur7_xxx on Friday October 21, 2016 @03:19AM (#12758730)
The vulnerability described by op applies to chrome just the same. Once the addon has `pageCapture` permission, an angular 1 exploit would work just the same.
Re:Angular 1.x Banned from Firefox Addons by emn13 on Friday October 21, 2016 @02:47PM (#12763383)
Many extensions have full access to all webpages, also in chrome; there's no sandbox or anything similar safely separating extension from page. That's not a bug or missing feature: it's by design! Many extensions fiddle with all kinds of page aspects as part of their core functionality.

An adblocker that can't inspect the page dom would likely not work very well.