Closed
Bug 1873653
Opened 2 years ago
Closed 2 years ago
[Experiment] The “Explore add-ons” button from the “Recommended Add-ons - Staff Pick” feature callout is partially overlapping the callout’s string while the button is being focused
Categories
(Firefox :: Messaging System, defect)
Tracking
()
VERIFIED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox121 | --- | unaffected |
| firefox122 | --- | unaffected |
| firefox123 | --- | unaffected |
People
(Reporter: avarro, Unassigned)
References
Details
Attachments
(1 file)
|
32.47 KB,
image/png
|
Details |
[Affected versions]:
- Firefox Release 118.0 - Build ID: 20230918143747, en-* locales
[Affected Platforms]:
- Windows 10x64
- Windows 11 x64
- macOS 13.6
- Ubuntu 22.4
[Prerequisites]:
- Have a new Firefox profile created and opened.
- Have this “user.js” file saved on your computer.
[Steps to reproduce]:
- Navigate to the “about:support” page and paste the “user.js” file into the User Profile.
- Restart the browser (Ctrl/Cmd + Shift + J and Ctrl/Cmd + Option + R).
- Open a new tab and observe the elements displayed.
[Expected result]:
- The “Recommended Add-ons - Staff Pick” feature callout is correctly displayed on the page while the “Explore add-ons” button is focused.
[Actual result]:
- The “Explore add-ons” button is partially overlapping the callout’s string while the button is being focused.
[Notes]:
- This issue is only reproducible on the Treatment A branch of the experiment.
- This issue is not reproducible on newer versions of Firefox.
- Attaching a screenshot of the issue.
[Regression Window]:
- Using Mozregression tools we have found a Pushlog link.
From this it looks like Bug 1842366 was fixed for Firefox 119 and above versions.
Comment 1•2 years ago
|
||
Setting Regressed by field after analyzing regression range found by mozregression in comment #0.
Keywords: regression
Regressed by: 1842366
Updated•2 years ago
|
Keywords: regression
No longer regressed by: 1842366
| Reporter | ||
Comment 2•2 years ago
|
||
I'm closing this issue as verified - fixed since the minimum targeted version has changed to Fx 119 and the users won't encounter this issue anymore.
Thanks!
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
| Reporter | ||
Updated•2 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•