Closed
Bug 1493561
Opened 6 years ago
Closed 2 years ago
non-specified border-width on input element is wide on Ubuntu
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox64 | --- | affected |
People
(Reporter: karlcow, Unassigned)
References
()
Details
(Whiteboard: [webcompat])
This is a spin-off of https://webcompat.com/issues/18994
0. With Firefox Nightly on Ubuntu
1. Go to http://www.resa.be/client/releve-d-index/
2. Notice how the first 4 digits are not visible at all. (see screenshots on https://webcompat.com/issues/18994 )
On the layout tab, without specifying a border there is:
on macOS:
margin: 0
border: 3px (while the default seems to be 2px ???)
padding: 1px
content: 9px x 13.5px
on Ubuntu reporter screenshot (without specifying border-width)
margin: 0
border: 0 8px 0 8px (!!!!)
padding: 1px
content: 0px x 32px
Once the reporter specified border-width: 0,
margin: 0
border: 0
padding: 1px
content: 15px x 18px
Comment 1•6 years ago
|
||
Well, it's clearly a bug in the page styling since they specify "width:17px"
on these themed <input>s (which by default has 'box-sizing:border-box') and
the theme may set an *arbitrary* wide padding/border.
Replacing "width:17px" with ""width:1ch; box-sizing:content-box;" is
probably what they intended. Or simply removing "width:17px" altogether
works too.
That said, I wonder if we should put a cap on themed padding/border values
because of page errors like this. They do seem too large to be
web-compatible on Ubuntu.
Comment 2•6 years ago
|
||
(or simply ignore themed padding/border-width values, which I'm guessing
is what Chrome does)
Comment 3•5 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
Comment 4•5 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Updated•5 years ago
|
Webcompat Priority: ? → revisit
Comment 5•2 years ago
|
||
We no longer use system-provided form rendering on linux, so this is no longer an issue.
Status: NEW → RESOLVED
Closed: 2 years ago
Webcompat Priority: revisit → ---
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•