Re:Mozilla shouldn't copy Chrome's permission prompt for ext...
by DougBTX on Sunday July 03, 2016 @06:17AM
(#12025490)
That's close to the content blocker api in Safari: https://webkit.org/blog/3476/content-blockers-first-look/
Re:Mozilla shouldn't copy Chrome's permission prompt for ext...
by robryk on Sunday July 03, 2016 @06:53AM
(#12025592)
It could still exfilter information if it could share any state between domains: the evil adblocker is associated with a site that many users visit. The site makes a lot of requests when it's loaded and adblocker exfiltrates information by selectively blocking those requests.
Re:Mozilla shouldn't copy Chrome's permission prompt for ext...
by roblabla on Sunday July 03, 2016 @05:55AM
(#12025424)
The problem is, many adblockers also have a feature to disable certain DOM nodes inside websites, to avoid embedded ads or remove anti-adblockers. So you'd also need an API to filter out certain selectors... And the list of specialized APIs could continue on and on.
Re:Mozilla shouldn't copy Chrome's permission prompt for ext...
by madeofpalk on Sunday July 03, 2016 @09:44AM
(#12026014)
Apple kind of solved this problem with the Content Blocker API - all of this is defined in a 'static' list which is used by Safari to block certain things.
Re:Mozilla shouldn't copy Chrome's permission prompt for ext...
by iancarroll on Sunday July 03, 2016 @10:19AM
(#12026127)
Chrome has an API for this, IIRC. They still need to connect to the internet to update their rule lists, though.
This seems like an API failure that common jobs for extensions can't be done without scary permissions.