Focus rings randomly displayed on all links until firefox is restarted
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: hitsinvimpula, Assigned: emilio)
References
Details
Attachments
(1 file, 1 obsolete file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
Since around a few versions ago, after running firefox for a random period of time
Actual results:
Focus rings start to appear on all clicked links even though they are turned off in about:config
Expected results:
Focus rings are not displayed
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Assignee | ||
Comment 2•2 years ago
|
||
What pref are you using to turn them off?
Reporter | ||
Comment 3•2 years ago
|
||
browser.display.show_focus_rings and browser.display.focus_ring_on_anything are both in their default state (false).
Assignee | ||
Comment 4•2 years ago
|
||
Assignee | ||
Comment 5•2 years ago
|
||
The only thing that can explain this is the WM_UPDATEUISTATE state
getting out of sync in a way that we think we need to unconditionally
show focus indicators for a window.
I tried to first make this less error prone (see patch above) but
digging more into these messages, I'm pretty sure we just don't need all
this code. See:
- https://devblogs.microsoft.com/oldnewthing/20130516-00/?p=4343
- https://devblogs.microsoft.com/oldnewthing/20130517-00/?p=4323
In particular, this is intended to be a windows feature to not show
keyboard indicators on dialogs until you use the keyboard. But that's
how Gecko dialogs behave already due to how :focus-visible behaves as
per:
I haven't been able to repro this state, but sounds believable that it
could happen after opening a native dialog or so on?
Instead of trying to fix this and untested code, let's just remove it. I
don't think it has any meaningful behavior difference as per the above,
and I also confirmed that other browsers don't handle this message.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 7•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Description
•