Tooltip on ETP Shield Icon turns into a black square after a restart from about:profiles
Categories
(Firefox :: Protections UI, defect, P3)
Tracking
()
People
(Reporter: oardelean, Unassigned)
References
(Regression, )
Details
(Keywords: regression)
Attachments
(1 file)
147.22 KB,
image/png
|
Details |
Found in
- Firefox 106.0b3
Affected versions
- Firefox 106.0b3;
- Firefox 105.0.1;
Tested platforms
- macOS 10.14
- Windows 8.1/10/11
- Ubuntu 22.04
Affected platforms
- macOS 10.14
- Windows 8.1/10/11
- Ubuntu 22.04
Unaffected platforms
- N/A
Steps to reproduce
- Launch Firefox and go to a page which has no trackers blocked, such as https://www.example.org .
- Hover over the ETP Shield Icon at the left of the address bar.
- Go to about:profiles and click on the "Restart Firefox" buttton.
- Go back to https://www.example.org tab.
- Hover over the ETP Shield Icon at the left of the address bar.
Expected result
- " No trackers known to Firefox were detected on this page" tooltip should show.
Actual result
- Tooltip isn't visible anymore.
Regression range
- Will look for one ASAP.
Additional notes
- Once the user opens a new tab and then returns to https://www.example.org , the tooltip is visible again. Doesn't reproduce by restart from keyboard shortcuts. Latest Nightly seems to be unaffected.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
mozregression points to:
-
last good: 2022-03-25
-
first bad: 2022-03-26
-
regressed by: bug 1728332
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1728332
:nika, since you are the author of the regressor, bug 1728332, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Comment 3•2 years ago
|
||
(In reply to Ardelean Oana from comment #0)
Latest Nightly seems to be unaffected.
When did this get fixed on nightly?
When this reproduces, are there any errors in the browser console?
Reporter | ||
Comment 4•2 years ago
|
||
Hello,
These are the errors thrown into the browser console after reproducing:
can't access property "firefoxVersion", b is null mozjexl.js:1 Identifier resource://gre/modules/components-utils/mozjexl.js:1
[Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getStringPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource://activity-stream/lib/ASRouter.jsm :: _remoteSettingsLoader :: line 287" data: no] ASRouter.jsm:287:28 _remoteSettingsLoader resource://activity-stream/lib/ASRouter.jsm:287 InterpretGeneratorResume self-hosted:1505 AsyncFunctionNext self-hosted:715
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById]
It seems that the fix in Nightly landed sometime in July 15 because from July 15 onwards I can't reproduce it anymore, not on the builds I tested at least. It is still reproducible on 106.0b6. I got the pushlog for further looking.
Please let me know If I can help with anything else. Thank you.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Set release status flags based on info from the regressing bug 1728332
Reporter | ||
Comment 7•2 years ago
|
||
Yes - 107.0b2 is affected on all three platforms - specifically macOS 12, Windows 10, Ubuntu 22.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 8•1 year ago
|
||
I can reproduce on 106.0.5 (64-bit) on Ubuntu 22.04. Can't reproduce on Nightly.
Worth fixing, but it seems to fix itself after tab-switch so not super concerning.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•11 months ago
|
Comment 9•11 months ago
|
||
I can no longer reproduce this bug on Firefox 113 on macOS and Ubuntu. Can we close it?
Reporter | ||
Comment 10•11 months ago
|
||
Could not reproduce either on Firefox 113.0.1 on macOS 12, Windows 10, Ubuntu 22.
Closing as RESOLVED WORKSFORME.
Updated•11 months ago
|
Description
•