Closed Turhvjbufv closed 1 month ago
This has been annoying me too, in a13
, a15
, & now also in a16
.
There's a parallel bug, also in Privacy & Security
; the setting Query OCSP responder servers to confirm the current validity of certificates
also toggles itself back Off with each Zen launch.
ArchLinux KDE Plasma
.
Both problems continue in a17
& a18
.
Both problems continue in
a17
&a18
.
As long as it's not closed as completed this bug will continue to appear, no point in spamming here
I am not spamming; this is a legitimate status update. With the just-arrived 1.0.0-a.22
, it seems the bug is now 50% solved:
Enhanced Tracking Protection
now retains its Strict
option enabled, across restarts :+1: Query OCSP responder servers to confirm the current validity of certificates
unfortunately still reverts to disabled after restarts :cry: Enhanced Tracking Protection would turn back to restrict when set to standard.
Waterfox has the same issue. See https://github.com/BrowserWorks/Waterfox/issues/3196.
In Zen's case, my user.js
sets ETP to Strict
on launch, but it still acts like Standard
ETP. For example, have Firefox and Zen open side-by-side with Strict
enabled and compare what's blocked in the shield icon on Pokemon Center and Bing.
Enhanced Tracking Protection
now retains itsStrict
option enabled, across restarts 👍
It doesn't, at least not anymore.
Enhanced Tracking Protection
now retains itsStrict
option enabled, across restarts 👍It doesn't, at least not anymore.
Oh? Mine remains good [since i first posted of it being fixed], including in the latest a.35
now. Sadly though, the similar part of the bug Query OCSP responder servers to confirm the current validity of certificates
remains a problem.
/opt/
.
Enhanced Tracking Protection
now retains itsStrict
option enabled, across restarts 👍It doesn't, at least not anymore.
Oh? Mine remains good [since i first posted of it being fixed], including in the latest
a.35
now. Sadly though, the similar part of the bugQuery OCSP responder servers to confirm the current validity of certificates
remains a problem.
- What's your platform? Mine's ArchLinux KDE Plasma.
- What's your installation mode? Mine's the tarball, downloaded, extracted & moved to
/opt/
.- Have you retested with a clean profile?
Mines windows(latest) and yep still doesn't work
windows(latest) and yep still doesn't work
I wonder if @onthejobtraining might also be using windows then...
* What's your platform? Mine's ArchLinux KDE Plasma.
Windows 11
* What's your installation mode? Mine's the tarball, downloaded, extracted & moved to `/opt/`.
Installed the fast version via zen browser website
* Have you retested with a clean profile?
Yes.
edit: Latest Zen 1.0.0-a.35
Ah, so [albeit from a statistically insignificant sample size] atm the common factor is windoze, whereas it is fixed in the Linux builds.
Sadly though, the similar part of the bug
Query OCSP responder servers to confirm the current validity of certificates
remains a problem.
I might have solved it.
However, similar to the ETP issue, just because you force enable it with the user.js doesn't mean it's actually working.
doesn't mean it's actually working
Yes indeed, your point seems utterly valid to me, but sadly i'm not knowledgeable enough to now be able to advance this matter any further. I hope the Dev can solve it, & in such a way that users can verify it's truly working.
For me, restarting Zen resets the Enhanced Tracking Protection from Strict to Custom.
@mauro-balades
I think this and #1941 can be closed now, as it appears it is resolved in 1.0.1-a.8.
Thanks!
I tried testing it on 1.0.1-a.8 by opening Pokemon Center on Firefox and Zen side-by-side and comparing what's blocked, as suggested by @yokoffing in their comment. But the tracking content blocked didn't match.
Can someone else test it and report their findings?
@sjclayton @mauro-balades The settings may be remembered, but the functionality still isn't working.
cnn.com
.@yokoffing
The functionality is very clearly working in some way... because look, I enabled Strict on Saturday, as evidenced below:
I tried testing it again on 1.0.1-a.17 using cnn.com and while trackers are being blocked by both Firefox and Zen, the number of trackers marked as blocked is higher on Firefox than on Zen.
Do we have a conclusion here on whether it's an issue with the blocking in Zen, the UI or simply the testing methodology?
What happened?
Settings it to strict, the setting won't be remembered when closing zen, and when opening zen again the setting will be resetted to standard, custom works tho and won't be resetting
Reproducible?
Version
1.0.0-a15
Severity impact
High
What platform are you seeing the problem on?
Windows
Relevant log output
No response