<select size=1> inline-size is too narrow when it renders a display:none <option>
RESOLVED
FIXED
in Firefox 65
Status
()
People
(Reporter: mats, Assigned: mats)
Tracking
({testcase})
Bug Flags:
Firefox Tracking Flags
(firefox64 wontfix, firefox65 fixed)
Details
Attachments
(2 attachments)
|
1.13 KB,
text/html
|
Details | |
|
4.78 KB,
patch
|
jwatt
:
review+
|
Details | Diff | Splinter Review |
The two <select>s in the testcase renders exactly the same in Edge, Chrome, and Safari, respectively. In Firefox, the 2nd <select> in each set appears to have a too narrow content-box inline-size.
|
(Assignee) | |
Comment 1•5 months ago
|
||
Actually, you'll need a fix for bug 1499127 to see the <option> in the 2nd <select> at all...
Depends on: 1499127
|
|
(Assignee) | |
Updated•5 months ago
|
Summary: <select> inline-size is too narrow when it renders a display:none <option> → <select size=1> inline-size is too narrow when it renders a display:none <option>
|
|
(Assignee) | |
Comment 2•5 months ago
|
||
FYI, this also fixes the bug on Android, but I'm skipping the reftest there because the -ref renders differently there for some *other* reason. (Presumably because of some weird rule in mobile/android/themes/geckoview/content.css as usual.)
Assignee: nobody → mats
Attachment #9019836 -
Flags: review?(jwatt)
|
||
Updated•5 months ago
|
Attachment #9019836 -
Flags: review?(jwatt) → review+
Pushed by mpalmgren@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/a218f406da67 Add some inline-axis padding after the <select size=1> display frame to avoid the text being flush to the dropdown button when we have a display:none <option>. r=jwatt
|
|
(Assignee) | |
Updated•4 months ago
|
Flags: in-testsuite+
|
||
Comment 4•4 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/a218f406da67
Status: NEW → RESOLVED
Last Resolved: 4 months ago
status-firefox65: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
|
||
Updated•4 months ago
|
status-firefox64: affected → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•