127882 - AOL Screen name and Password box display in wrong spot and when enter text they jump 2 inches up the page.

Status: VERIFIED DUPLICATE of bug 126742

(Core :: Layout, defect, P1)

Description

[TucsonTester3]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.8+)
Gecko/20020225 Netscape6/6.2.1+
BuildID:    2002022503

In the page  http://www.aol.com/  , The Screen name and Password form is
displayed where the Mail, Portfolio, My AOL, and Calendar icons should. Once you
enter text into ether box the form jumps to where it should display. Upon
minimizing and maximizing the page is displayed correctly. I didn't see this on
this build in Win XP.

Reproducible: Always
Steps to Reproduce:
1.Start Netscape
2.Navigate to http://www.aol.com/
3.

Actual Results:  Screen name and Password form is displayed where the
Mail,Portfolio,My AOL, and Calendar icons should.

Expected Results:  Screen name and Password should display above icons

Comment 1

[Boris Zbarsky [:bzbarsky]]

layout

Comment 2

[Kevin McCluskey (gone)]

nsbeta1+

Comment 3

[Marc Attinasi]

According to my testing, this regressed sometime between the 17th and the 20th -
promoting to CRITICAL and continuing to search for the culprit.

Comment 4

[Marc Attinasi]

works fine using 2002021803, but is broken on 02/19 build.

Comment 5

[Marc Attinasi]

*** Bug 126951 has been marked as a duplicate of this bug. ***

Comment 6

[karnaze (gone)]

This could be a dup of bug 126742 which landed yesterday afternoon. I have that 
patch in my build and I'm not seeing the problem.

Comment 7

[Chris Petersen]

Attachment: Reduced test case

Nested table pushes outside of parent table.

Comment 8

[Chris Petersen]

The nested table has a width and height specified <table width=375 height=250
border="2">. The parent table doesn't have a width or height declared.

Comment 9

[karnaze (gone)]

Petersen, please verify with a recent build.

*** This bug has been marked as a duplicate of 126742 ***

Comment 10

[TucsonTester3]

Verified

Comment 11

[Chris Petersen]

Problem is fixed. Verified in the Feb 27th build (2002-02-27-03)