16297 - INPUT text is too large in standard mode

Status: VERIFIED FIXED

(Core :: Layout: Form Controls, defect, P3)

Description

[Masatoshi Kimura [:emk]]

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).

Comment 1

[Masatoshi Kimura [:emk]]

Attachment: testcase

Comment 2

[Masatoshi Kimura [:emk]]

Attachment: screenshot using M10 viewer

Comment 3

[cpratt]

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...

Comment 4

[Masatoshi Kimura [:emk]]

Attachment: screenshot using M11 viewer

Comment 5

[Masatoshi Kimura [:emk]]

Attachment: screenshot using M10 viewer

Comment 6

[Masatoshi Kimura [:emk]]

Attachment: screenshot using recent nightly build viewer

Comment 7

[Masatoshi Kimura [:emk]]

Sorry. first and second screenshots are corrupted. Ignore them.
Recent build's input is larger than M10's one.

Comment 8

[karnaze (gone)]

Reassigning to Rod.

Comment 9

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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?

Comment 10

[rods (gone)]

It is no longer too big. MArking fixed

Comment 11

[cpratt]

Agreed.