6695 - width does not work on input fields, textareas

Status: VERIFIED FIXED

(Core :: CSS Parsing and Computation, defect, P3)

Description

[Archimedes Trajano]

See attached file.

In the first field on the right side it seems to be larger than 97px.  The page
renders properly in IE5

It also seems to ignore that I want the border of the element to be 1px

For some strange reason the field labels are white on white text.

Comment 1

[Archimedes Trajano]

Attachment: test page

Comment 2

[John Morrison]

[e-mail]: You might try submitting that attachment again. You have
a linked stylesheet in the page, that does not resolve to the true location
of 'stylesheet.css'. It's a little difficult to comment without the contents
of the css file.

As far as the Label (white on white) goes, that is bug #3720.

Comment 3

[Archimedes Trajano]

Attachment: Style sheet

Comment 4

[karnaze (gone)]

I can't load the attachment. Reassigning to Eric.

Comment 5

[Christian Wenz]

Attachment: the style sheet as text/html

Comment 6

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

Is this fixed by GFX widgets?

Comment 7

[Micah Dubinko]

Attachment: Test case that doesn't have external dependencies

Comment 8

[Micah Dubinko]

Testscase shows width not working for <input> fields. Uses inline styles instead
of a style sheet. Problem exists as tested, on vanilla M8 and 19990821 nightly
build, Win98. (Use IE 4 or 5 to compare)

Comment 9

[Eric Pollmann]

I am able to reproduce this bug - in the reduced test case, both text input
elements render at something like 1.5 inches wide even though CSS specifies
their width to be .25 and .75 inches wide respectively.  Can you guys take a
look?  Thanks!

Comment 10

[buster]

rod is looking into text control sizing issues.  in fact, this may already
be fixed.
take it away, rod!

Comment 11

[Christine Hoffman]

Using the 8/21 test case with the 10/20 app, problem does not appear to be
fixed. Edit boxes are the same width. Reopening bug.

Comment 12

[rods (gone)]

I tested it in NavQuirks and Standard mode - fixed

Comment 13

[Christine Hoffman]

Using 11/1 Apprunner, verified bug is now fixed.