-
Notifications
You must be signed in to change notification settings - Fork 970
webrequest filtering functions not working in Tor mode #14021
Comments
Was testing on Windows 10 - observed some behavior worth noting in case it helps with this. I began browsing with scripts disabled to get a feel for the edges between ads and no ads with the Tor connection, and observed a tracking pixel being blocked with scripts disabled. Details and STR below. profile: Brave: 0.23.2 STR:
I re-enabled scripts and reloaded the page. I observed what appears to be a mix of ad and tracking calls blocked on that page (scripts re-enabled): I navigated to the homepage, and observed ad and tracking requests being blocked on the homepage with scripts enabled: When I attempted to repro the same way from a separate Tor tab (same str as listed above) - I'm observing different results, zero requests blocked across all shield stats. I navigated to an article page from the same tab that showed zero blocking and did not observe any blocked ads or tracking from an article page. Note that I have site isolation enabled in this build as well. Not sure why I'm seeing different results from the same steps to repro in different Tor tabs, but fwiw did not recall observing tracking protection working until after I began disabling scripts for the tor tab that began blocking things. |
fixed by brave/muon@750df85 which will be available in muon 6.1.1 |
STR:
It looks like the partition is initialized, but the webrequest listeners in the Tor session do not fire.
cc @darkdh @riastradh-brave
The text was updated successfully, but these errors were encountered: