270073 - strange gap (misrendering?) between field elements introduced with firefox 1.0

Status: RESOLVED INVALID

(Core :: Layout: Floats, defect)

Description

[Christian Ertl]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

http://www.mosnet.de/volmer2/kontakt.php shows a gap between input fields
"Vorname" and "Nachname".
This didn't happen with 0.9.3.

This behaviour is also experienced by other users.
(German: http://firefox.stw.uni-duisburg.de/forum/viewtopic.php?t=10260)

There doesn't appear to be something in the source of the page causing this.

Reproducible: Always
Steps to Reproduce:
1. Load http://www.mosnet.de/volmer2/kontakt.php.


Actual Results:  
There is a gap between first pair of field elements.

Expected Results:  
There should be the same distance as between the other fields.

Comment 1

[Bill Mason]

Also visible in 20041115 trunk.

Comment 2

[Bill Mason]

Attachment: testcase

Comment 3

[Bill Mason]

That rendering looks right to me.

The code calls for the float to be cleared after the <br> of the first form
field.  So clearing the float of the left menu puts the next field below the menu.

I think this is invalid, or a TE bug.

Comment 4

[Uri Bernstein]

Attachment: testcase 2

This is almost the same as the previous tescase, except it has "width:555px" on
the "content" div. This causes it to behave "correctly" (no gap) on IE, like
the original page. 
The previous testcase shows a gap on IE, just like on Firefox.

Comment 5

[Uri Bernstein]

The current behaviour is a result of the fix to bug 148994, and, according to
the comments on that bug, is the correct implementation of the standard.

I personally think that the standard is terribly counter-intutive and "wrong"
here, but there's nothing to do about that.
So I'm sadly marking this INVALID.

However, it's interesting that IE seems to behave differently when a width is
set on the div containing the cleared element (see testcase #2, in IE). Perhaps
we should implement this as a quirck?