Blocked tracker count incorrectly persists across tab switches to another site
Categories
(Firefox :: Protections UI, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox153 | --- | unaffected |
| firefox154 | --- | unaffected |
| firefox155 | + | fixed |
| firefox156 | + | fixed |
People
(Reporter: sam, Assigned: kandres)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [feltpy-show-trackers])
In the following scenario:
- browser.urlbar.trackerCountShown=true
- Tab 1 is open to site1.(domain.com) with 5 blocked trackers
- Tab 2 is open to site2.(domain.com) with 0 blocked trackers
When switching from tab 1 to tab 2, the URL bar blocked tracker count incorrectly persists at 5 blocked trackers, even though clicking to open the trust panel shows no trackers blocked.
The opposite direction, however, works fine: Switching from tab 2 to tab 1 correctly changes from showing 0 blocked trackers to 5 blocked trackers.
Switching to a non-(domain.com) tab also correctly changes the blocked tracker count. Switching from the non-(domain.com) tab to tab 2 also works correctly.
Comment 1•23 days ago
|
||
Set release status flags based on info from the regressing bug 2051545
:Vincent, since you are the author of the regressor, bug 2051545, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•22 days ago
|
Comment 2•20 days ago
|
||
This seems like something we should fix before this feature goes out the door.
Comment 3•17 days ago
|
||
The bug is marked as tracked for firefox155 (beta) and tracked for firefox156 (nightly). However, the bug still isn't assigned.
:cbellini, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Updated•17 days ago
|
Comment 4•17 days ago
|
||
Pretty minor UX issue that doesn't impact use of the browser. Optional for 155. FYI to owners, this still has not been triaged and 155 is now in Beta!
Updated•17 days ago
|
Should be fixed by https://phabricator.services.mozilla.com/D313753
The above patch has landed, and I can no longer reproduce in Nightly.
Updated•14 days ago
|
Comment 8•14 days ago
•
|
||
The current status for this bug is RESOLVED FIXED, so no. That said, I'd still love to get an uplift request soon for bug 2057267 so it can be fixed for 155 as well.
Updated•13 days ago
|
Description
•