about:preferences dialog close buttons shouldn't be focusable
Categories
(Firefox :: Settings UI, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox64 | --- | unaffected |
firefox65 | --- | wontfix |
firefox66 | --- | wontfix |
firefox67 | --- | wontfix |
firefox68 | --- | wontfix |
firefox69 | --- | fix-optional |
People
(Reporter: cfogel, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
19.80 KB,
image/png
|
Details |
Note
- The main issue is that the on-hover and on-click effects are of different widths and it looks wierd
Affected versions
- 65.0b12
- 66.0a1
Affected platforms
- Windows 10
- Ubuntu 18.04
Steps to reproduce
- Access about:preferences#privacy
- Click on the Saved Logins button;
- Click inside the Search field;
- Click and hold on the X button;
- Holding the button pressed, move the mouse down;
- Repeat steps 3+5;
Expected result
- effects should have the same size;
Actual result
- the on-click effect width is increased;
Regression range
- First bad: 2018-12-08 16:50:31.162000
- Last good: 2018-12-08 11:30:00.887000
- Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a4c37fbac068d2e4e250d0d90c3c0f4c9129d8b0&tochange=09493e80dbe7c1486eb3c93960cc81f73c8c5356
- Potential regressor: bug 1511394
Additional notes
- 64.0.2 not affected;
- macOS is not affected by this issue;
- attached screenshot with this issue;
Reporter | ||
Comment 1•5 years ago
|
||
Updated summary and STR.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
This button shouldn't be focusable in the first place.
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Happy to take a patch in nightly or even in beta 66 for this.
I'm marking it fix-optional to remove it from weekly triage.
Reporter | ||
Comment 4•5 years ago
|
||
Updating flags as it's still reproducible on current versions.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Cristian - when we mark something wontfix and fix-optional across all versions, it means we don't want to keep marking it affected or keep triaging it. (See Comment 3) We know it hasn't been fixed, but it already has a priority assigned by the triage owner or someone on a related team.
So, please don't mark new versions affected in cases like this, because that means that we see it over and over again in triage. Unless it's a P1 issue that you think it's important to bring back to everyone's attention :)
Reporter | ||
Comment 7•4 years ago
|
||
With macOS 10.15.3, just noticed that this issue reproduces with 76.0 as well.
Updated•2 years ago
|
Description
•