Open
Bug 1534231
Opened 5 years ago
Updated 2 years ago
[win] menulist-button no longer displays the triangle icon
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox65 | --- | wontfix |
firefox66 | --- | wontfix |
firefox67 | --- | wontfix |
firefox68 | --- | fix-optional |
People
(Reporter: cfogel, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
56.28 KB,
image/png
|
Details |
Affected versions
- 67.0a1(Build ID_20190310214003), 66.0b15, 65.0.2;
Affected platforms
- Windows 10;
Steps to reproduce
- Access this link
- Click inside the dropdown for the Asset section;
Expected result
- the triangle icon for the dropdown is displayed;
Actual result
- the triangle icon for the dropdown is not displayed;
Regression range
- aTrif helped with getting the regression range:
- Potential regressor: bug 1480073
Additional notes
- attached screenshot with the issue;
- the **-webkit-appearance: menulist-button; (-moz-appearance: menulist-button;) ** appears to cause the icon to no longer be displayed;
- another good test case is with this link ; replacing -webkit-appearance: button; with -webkit-appearance: menulist-button;
- issue not encountered on Ubuntu and macOS;
Reporter | ||
Comment 1•5 years ago
|
||
Hey Jonathan, mind confirming the regression part if it's the case?
Thank you!
Has Regression Range: --- → yes
Has STR: --- → yes
Flags: needinfo?(jwatt)
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Bulk change for all regression bugs with status-firefox67 as 'fix-optional' to be marked 'affected' for status-firefox68.
status-firefox68:
--- → affected
Comment 4•5 years ago
|
||
We have bug 1481615 to align our behavior with Chrome, which would fix this. I'm not sure that's the highest priority right now though.
Depends on: 1481615
Flags: needinfo?(jwatt)
Updated•5 years ago
|
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•