Open
Bug 1477110
Opened 7 years ago
Updated 1 year ago
Select elements seem to get double the text-indent
Categories
(Core :: Layout: Form Controls, defect, P3)
Core
Layout: Form Controls
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | affected |
People
(Reporter: twisniewski, Unassigned)
References
Details
(Whiteboard: [webcompat])
Attachments
(3 files)
Select elements given a percentage text-indent seem to use twice the percentage specified (or at least this appears so in the attached test-case).
Chrome would seem to be using the expected amount.
This appears to be causing the interop issue in webcompat.com #8842.
I'm not certain if this is related at all to bug 1476051, but it happens regardless of whether -moz-appearance is used.
Flags: webcompat?
Comment 1•7 years ago
|
||
Odd! There are several helper-boxes involved in select elements -- I would bet we're applying the text-indent at two different levels (to two different nested helper-boxes), or something like that.
Priority: -- → P3
Comment 2•6 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
Comment 3•6 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Updated•5 years ago
|
Webcompat Priority: ? → revisit
Comment 4•5 years ago
|
||
This also occurs for px text-indent values, in the latest Firefox (82.0.2 (64-bit)) and on macOS 10.15.7.
Attached is an updated test which shows both cases. The first select box should have its value printed in the middle of the third marker, while the second select box should have its value aligned with its second marker.
Updated•4 years ago
|
Summary: Select elements seem to get double the text-indent when a percentage is specified. → Select elements seem to get double the text-indent
Comment 6•4 years ago
|
||
Here's a testcase based on the jsfiddle from dupe bug 1743066.
Updated•3 years ago
|
Webcompat Priority: revisit → P3
Updated•3 years ago
|
Severity: normal → S3
Comment 7•1 year ago
|
||
This is still a valid issue as testcases still reproduce - however, we don't have any active non-testcase WebCompat breakage caused by this. Unsetting the webcompat-priority flags per our rules.
Webcompat Priority: P3 → ---
Flags: webcompat?
You need to log in
before you can comment on or make changes to this bug.
Description
•