Closed
Bug 16297
Opened 25 years ago
Closed 25 years ago
INPUT text is too large in standard mode
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: emk, Assigned: rods)
Details
Attachments
(5 files)
screenshot using M10 viewer
Steps to reproduce:
1. Launch viewer in standard mode.
2. Go to the following testcase.
Actual result:
<INPUT text> seems to too large.
I'm using the [1999101208] build viewer on WinNT4 (SP5).
|
Reporter | |
Comment 1•25 years ago
|
||
|
|
Reporter | |
Comment 2•25 years ago
|
||
that is, the text input control itself seems to large, and I concur. it seems to
have room for about 1.75 lines of text in it; compare it side-by-side with Nav
4.x...
|
|
Reporter | |
Comment 4•25 years ago
|
||
|
|
Reporter | |
Comment 5•25 years ago
|
||
|
|
Reporter | |
Comment 6•25 years ago
|
||
|
|
Reporter | |
Comment 7•25 years ago
|
||
Sorry. first and second screenshots are corrupted. Ignore them.
Recent build's input is larger than M10's one.
|
||
Updated•25 years ago
|
Assignee: karnaze → rods
|
|
||
Comment 8•25 years ago
|
||
Reassigning to Rod.
|
||
Comment 9•25 years ago
|
||
Perhaps the problem here is the illegal statement in ua.css (actually in
html.css):
font-size: 10;
There are no units, so this declaration should be ignored in standard mode.
IMO, you shouldn't use numbers at all in ua.css, but rather keywords
small/medium/large, etc., like most of the other uses of font-size in ua.css.
grep font-size html.css
shows only 4 uses of numbers for font size - and two of those numbers don't have
units and should therefore be ignored.
Should ua.css be parsed in the same mode (standard) whether or not the document
is in compat mode?
|
Assignee | |
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 10•25 years ago
|
||
It is no longer too big. MArking fixed
|
||
Comment 11•25 years ago
|
||
Agreed.
You need to log in
before you can comment on or make changes to this bug.
Description
•