[Windows] Some visual glitches can be seen on the forward page arrow when the Underline access keys setting is on
Categories
(Core :: Graphics, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox110 | --- | unaffected |
firefox111 | --- | fixed |
firefox112 | --- | affected |
People
(Reporter: csasca, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Found in
- Firefox 112.0a1
Affected versions
- Firefox 111.0b6
- Firefox 112.0a1
Tested platforms
- Affected platforms: Windows 10
- Unaffected platforms: macOS, Ubuntu
Preconditions
- Have the setting "Underline access keys when available" on from the Keyboard section in Ease of access in Windows settings
Steps to reproduce
- Launch Firefox
- Access any random page
- Resize Firefox window or click on back page then forward or refresh the page
Expected result
- No parts of the underline is shown on the forward page arrow
Actual result
- Parts of the underline are shown when browsing or resizing Firefox window (might take a few tries to reproduce it)
Regression range
- Will see for a regression.
Additional notes
- The issue can be seen in the attachment.
- It's not reproducible 100% but it's easy enough to make it appear (may appear on the refresh button as well, can be seen for a moment in the attachment as well)
Updated•2 years ago
|
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Searched for regression and it pinpointed between 2023-01-19 and 2023-01-20. Further bisection gave the following informations:
Found commit message:
Bug 1753349 (9/9): chore: update ANGLE to our fork's firefox-111
branch r=jgilbert
Differential Revision: https://phabricator.services.mozilla.com/D162655
Comment 2•2 years ago
|
||
Setting 111 to fixed - regressor was backed out of beta via a patch on Bug 1817240
Comment 3•2 years ago
|
||
:ErichDonGubler, since you are the author of the regressor, bug 1753349, could you take a look?
For more information, please visit auto_nag documentation.
Comment 4•2 years ago
|
||
I suspect this is a similar root cause and symptom as 1817240. :ahale, what do you think here?
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Can you attach about:support for the affected system? This looks like the issue we saw on Intel Skylake, so I'd like to know if it's the same GPU or a different one. In theory Firefox Nightly should have the regression fix since it landed last night I believe.
Reporter | ||
Comment 6•2 years ago
|
||
Hey Ashley, sure thing, here's the about:support from 111.0.
Comment 8•2 years ago
|
||
:csasca: To add some context to :jrmuizel's question, it's possible that this is a dupe of 1817240, which has been fixed.
Comment 9•2 years ago
|
||
I was not able to reproduce the issue on any of the affected builds, Firefox 111.0b6 and Firefox 112.0a1, so I cannot confirm the fix.
Catalin will return from PTO on Monday and he will investigate this issue.
Reporter | ||
Comment 10•2 years ago
|
||
Hey guys, just tried on Firefox 112.0b9 and 113.0a1 (2023-04-02) and I can't reproduce it anymore on Windows 10. Seems that Bug 1817240 which Erich mentioned might have fixed this. Will close it as wfm in this case. Thanks!
Description
•