Closed Bug 1620531 Opened 4 years ago Closed 4 years ago

about:logins - have [Sort by] button share the same width as the dropdown menu

Categories

(Firefox :: about:logins, defect, P5)

defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr68 --- disabled
firefox73 --- wontfix
firefox74 --- wontfix
firefox75 --- wontfix
firefox76 --- wontfix

People

(Reporter: cfogel, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Attached image x.png

Affected versions

  • 70.0, 73.0.1, 74.0b8, 75.0a1 (2020-02-26);

Affected platforms

  • Windows 10, macOS 10.15, Ubuntu 19.04;

Steps to reproduce

  1. Launch Firefox, access about:logins
  2. Input any dummy_logins if none added in the list;
  3. Click on the [Sort by] button;

Expected result / Enhancement suggestion

  • dropdwn menu is of the same width as the button;

Actual result

  • dropdown menu width is greater than the button;

Regression range

  • Pushlog: URL;
  • Potential regressor: 1576029

Additional notes

  • attached screenshot with the issue;
Attached image reg.png

Rechecked if this is not a regression with build closer to the implementation and it looks like this is a regression.
Attaching a screenshot with the layout to better illustrate it.

Updated the regression section of the initial comment(macOS is a different case since the menu overlaps the button, but could still benefit from this if implemented).
Updating the status flags as well.

@ntim, mind taking a look at this?
Thanks!

Has Regression Range: --- → yes
Has STR: --- → yes
Flags: needinfo?(ntim.bugs)
Keywords: regression
Regressed by: 1576029

Bug 1576029 reduced the right padding from 24px to 16px since it was wanted by UX to have the select arrow closer to the text.

I'm guessing the Windows select popup has a min-width that causes this bug.

Redirecting to Jared/Matt since I'm not quite sure how actionable this is.

Flags: needinfo?(ntim.bugs)
Flags: needinfo?(jaws)
Flags: needinfo?(MattN+bmo)
Type: enhancement → defect

This seems like a low priority issue and is just demonstrating the "normal" behaviour for <select> elements on the web… there is no constraint from UX what the widths match.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(jaws)
Flags: needinfo?(MattN+bmo)
Priority: -- → P5
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.