$permissions · uBlockOrigin/uBlock-issues · Discussion #2714 (original) (raw)

@stephenhawk8054 Gave more thoughts to this and I think we should add it to uBlock filters -- Privacy list. I don't think a user interface component for this is the way to go given that so far it's an API supported only by one browser, and that the API is to serve advertisers in the first place.

You must be logged in to vote

15 replies

@uBlock-user

*$permissions=idle-detection=()|browsing-topics=()

That is a whole filter itself and should not be interpret as *$permissions=idle-detection=() and *$permissions=browsing-topics=(). So,

a exception filter would work look like this - @@*$permissions=idle-detection=()|browsing-topics=(),domain=example.org

@MasterKia

@uBlock-user These do work:

||google.com^$all @@||google.com^$doc

||google.com^$script,xhr,image @@||google.com^$script

$script,xhr,to=google.com|example.com @@$script,to=google.com

@uBlock-user

Those are individual network type filters. idle-detection=() is a policy not a network type filter. Here's there's only one network type, that is $permissions.

@gorhill

These do work

uBO does not have a permission policy value parser, and neither a CSP value parser, hence why the values can only be wholly excepted.

This has always been the way for CSP value, there was never a way to except only the script-src part of a filter such as *$csp=worker-src 'none';script-src 'none', and unsurprisingly it's also the case for permissions= option.

@stephenhawk8054