-
Notifications
You must be signed in to change notification settings - Fork 527
Wilcards in White/Blacklists #1474
Comments
How do you propose to solve this in a for everybody transparent way? |
Please not that there would be a significant performance impact for checking multiple levels, so that is not an option. |
If checking multiple levels is not an option then I am all out of ideas :( Since that is exactly what wildcards are for |
In theory, you could allow a user to switch between two whitelist/blacklist modes:
Or perhaps a combination of these modes. But I'm not sure this should have priority... I don't think it would matter to me, for now. |
I see no feasible solution to fix this, so I am setting this issue to won't fix. |
I completely agree and understand. |
I will see what I can do again. |
Test version: |
This version should shown one level of folders more: |
This new version works great, but it may cause issues on devices with small screens. I just had a popup that took up the whole screen on my note 2 with a large screen |
The on demand dialog is scrollable. |
Learn something new every day |
In White/Blacklists the wildcards () don't function the way wildcards usually do.
If I whitelist for example /sdcard/folder1/ anything in folder1 should be whitelisted. Howevever, if the destination is more than 1 subfolder away from folder1 (i.e. /sdcard/folder1/x/y) the wildcard rule does not apply.
The same goes for domains where *.google.com should also block abc.123.google.com
I hope this makes sense
The text was updated successfully, but these errors were encountered: