Open Bug 1521037 Opened 5 years ago Updated 2 years ago

about:preferences dialog close buttons shouldn't be focusable

Categories

(Firefox :: Settings UI, defect, P3)

defect

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)

Attached image about_prefXbtn.png

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

  1. Access about:preferences#privacy
  2. Click on the Saved Logins button;
  3. Click inside the Search field;
  4. Click and hold on the X button;
  5. Holding the button pressed, move the mouse down;
  6. Repeat steps 3+5;

Expected result

  • effects should have the same size;

Actual result

  • the on-click effect width is increased;

Regression range

Additional notes

  • 64.0.2 not affected;
  • macOS is not affected by this issue;
  • attached screenshot with this issue;

Updated summary and STR.

Summary: about:preferences menus close button has increased width → about:preferences menus close button has different width for on-click and on-hover effects
Blocks: 1511394
Priority: -- → P5

This button shouldn't be focusable in the first place.

Priority: P5 → P3
Summary: about:preferences menus close button has different width for on-click and on-hover effects → about:preferences dialog close buttons shouldn't be focusable
Has Regression Range: --- → yes

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.

Updating flags as it's still reproducible on current versions.

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 :)

Flags: needinfo?(cristian.fogel)

Roger, thanks for the info!

Flags: needinfo?(cristian.fogel)

With macOS 10.15.3, just noticed that this issue reproduces with 76.0 as well.

See Also: → 1633994
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: