Standard content blocking is highlighted regardless of what option is selected
Categories
(Toolkit :: Preferences, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | --- | verified |
firefox67 | --- | verified |
People
(Reporter: sdp.misc, Assigned: Gijs)
References
Details
(Keywords: regression, Whiteboard: [triagemonth-2019-02])
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
lizzard
:
approval-mozilla-beta+
|
Details | Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
- Load "about:preferences#privacy"
- Under "Content Blocking", select strict or custom
- Reload the page
Actual results:
The standard option is highlighted and expanded.
Expected results:
Strict or custom (whichever was selected) should be highlighted and expanded.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
I can reproduce this issue on Firefox 66 Beta and Firefox 67 Nightly but not in Firefox Release 65 in Windows 10, 64bit.
So, this must be a regression. I will try and find the regression range.
Comment 2•5 years ago
|
||
regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=33ca2ea6b37064d12c0d4fefc81bf689396a5e57&tochange=9ae7ae0acee4f8807cffaf64fef4f2e3a614b997
regressed by: Bug 1518252
Comment 3•5 years ago
|
||
Likely same fix as for bug 1524995. Zibi is investigating bug 1524995 currently.
Comment 4•5 years ago
|
||
Regression from bug 1520350. Reverting that patch fixes this bug.
Assignee | ||
Comment 5•5 years ago
|
||
(In reply to Zibi Braniecki [:gandalf][:zibi] from comment #4)
Regression from bug 1520350. Reverting that patch fixes this bug.
This doesn't make sense, because bug 1520350 is not on beta, and comment #1 and comment #2 says beta is affected.
Assignee | ||
Comment 6•5 years ago
|
||
(In reply to :Gijs (he/him) from comment #5)
(In reply to Zibi Braniecki [:gandalf][:zibi] from comment #4)
Regression from bug 1520350. Reverting that patch fixes this bug.
This doesn't make sense, because bug 1520350 is not on beta, and comment #1 and comment #2 says beta is affected.
... and indeed, I can reproduce on beta.
Comment 7•5 years ago
|
||
Thanks! Testing on beta.
Can you verify that with that patch reverted you cannot reproduce on Nightly?
Comment 8•5 years ago
|
||
I can't reproduce the bug in 66b5 I downloaded from https://ftp.mozilla.org/pub/firefox/releases/66.0b5/linux-x86_64/en-US/
Comment 9•5 years ago
|
||
I can still reproduce the issue on 66.0b5 Windows10 with new profile.
Build ID 20190204181317
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Comment 10•5 years ago
|
||
I was also able to reproduce it on Linux, but the behavior is:
- Open browser (66b5)
- Go to Preferences and select Strict policy and
Always use private browsing mode
- Restart browser
- Open Preferences
- Strict policy is selected and all three checkboxes under
Always use private browsing mode
are unchecked - ctrl+r to reload
- Now Standard policy is selected and two of the three checkboxes are checked
I see the same behavior in Nightly with the patch from bug 1520350 backed out.
So to sum up my current understanding:
- With bug 1520350 I see it reliably
- Without it, I see it after reload on both beta and nightly
That makes me think that there's some other underlying problem that potentially bug 1520350 made more visible.
Continue investigating.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 11•5 years ago
|
||
Comment 13•5 years ago
|
||
Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/autoland/rev/4ae67123a816 correctly select the right content blocking option, r=ewright
Comment 14•5 years ago
|
||
bugherder |
Assignee | ||
Comment 15•5 years ago
|
||
Comment on attachment 9042459 [details]
Bug 1525099 - correctly select the right content blocking option, r?johannh
Beta/Release Uplift Approval Request
Feature/Bug causing the regression
1520350, 1518252
User impact if declined
Confusing UI in the preferences/options
Is this code covered by automated tests?
Yes
Has the fix been verified in Nightly?
No
Needs manual test from QE?
Yes
If yes, steps to reproduce
See comment #0, comment 10
List of other uplifts needed
n/a
Risk to taking this patch
Low
Why is the change risky/not risky? (and alternatives if risky)
Very small, well-understood JS-only change to this specific bit of the preferences
String changes made/needed
no
Updated•5 years ago
|
Updated•5 years ago
|
Comment 16•5 years ago
|
||
Hello ,
I have reproduced this issue with the FF Nightly build from 2019-02-04.
This issue is verified fixed on the latest FF Nightly(buildID: 20190212095015) on Win 10x64,macOS10.11 and Ubuntu 18.04 x64.
Comment 17•5 years ago
|
||
Comment on attachment 9042459 [details]
Bug 1525099 - correctly select the right content blocking option, r?johannh
UI fix for content blocking options, verified in nightly.
OK for uplift for beta 8.
Comment 18•5 years ago
|
||
bugherder uplift |
Updated•5 years ago
|
Comment 19•5 years ago
|
||
I have re-verified this issue again in the 66.0b8(BuildID: 20190214102000 Build from taskcluster) on Win 10x64. Ubuntu 16.04 and macOS 10.12. Confirming this as verified fixed.
Updated•5 years ago
|
Description
•