Closed
Bug 1958396
Opened 1 year ago
Closed 1 year ago
[Windows] The arrow for a `menu` in menupopups is no longer aligned with the menuseparator
Categories
(Firefox :: Menus, defect)
Tracking
()
VERIFIED
FIXED
139 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox137 | --- | unaffected |
| firefox138 | --- | unaffected |
| firefox139 | --- | verified |
People
(Reporter: itiel_yn8, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
This is because there's an extra padding on the inline-end side now, whereas it was only on the inline-start side.
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1954977
:emilio, since you are the author of the regressor, bug 1954977, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
status-firefox137:
--- → unaffected
status-firefox138:
--- → unaffected
status-firefox139:
--- → affected
status-firefox-esr128:
--- → unaffected
Flags: needinfo?(emilio)
| Assignee | ||
Comment 2•1 year ago
|
||
Don't artificially push the arrow and such 1em to the right, now that's
accomplished by padding on the item.
Updated•1 year ago
|
Assignee: nobody → emilio
Status: NEW → ASSIGNED
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → emilio
Flags: needinfo?(emilio)
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7e7a4ec8e270
Fix arrow / acceltext alignment on Windows after recent changes. r=desktop-theme-reviewers,Itiel
Comment 4•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-triage-done-c140/b139][qa-verif-needed-c140/b139]
Flags: qe-verify+
Updated•1 year ago
|
QA Whiteboard: [qa-triage-done-c140/b139][qa-verif-needed-c140/b139] → [qa-triage-done-c140/b139][qa-ver-needed-c140/b139]
Updated•1 year ago
|
QA Contact: bmaris
Comment 5•1 year ago
|
||
Reproduced the behavior from comment 0 using an old Nightly 'he' build from 2025-04-03, verified that using the latest Nightly 140.0a1 and the latest beta build 139.0b1 this is now fixed, also checked the 'en-US' build as well.
Status: RESOLVED → VERIFIED
QA Whiteboard: [qa-triage-done-c140/b139][qa-ver-needed-c140/b139] → [qa-triage-done-c140/b139][qa-ver-done-c140/b139]
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•