Closed Bug 2601 Opened 26 years ago Closed 26 years ago

http://disney.go.com/: chrome box at top does not lay out properly

Categories

(Core :: DOM: HTML Parser, defect, P2)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: christinehoff4, Assigned: rickg)

References

()

Details

Using the 1_21 build on Win 95, Win NT, Win 98 and Mac 8.5 (linux not tested): Open the above URL. Expected results: 1) the following event handler links should display in the chrome at top: 'GO Entertainment', 'GO Family', 'GO Money', 'GO News', 'GO Sports', 'GO Home' 2) the following event handler links should display inside the chrome box: 'About Go Network', 'Sign-in', 'Free E-mail'. 3) Search button should layout to the right of the Search text box Actual results: 1) only 'GO Entertainment', 'GO Family' links display. 2) About 'Go Network', 'Sign-in', 'Free E-mail' display outside the chrome box 3) Search button displays under the Search text box
Assignee: troy → rickg
Component: Layout → Parser
Looks like a parser problem
Status: NEW → ASSIGNED
Summary: [PP] http://disney.go.com/: chrome box at top does not lay out properly → http://disney.go.com/: chrome box at top does not lay out properly
This is not a platform parity bug. I'm removing that status from this report, but accepting the bug.
FWIW, the parser breaks on the mismatch of an opening <TH> with a closing </TD>. Look for this line (about line 98 in the content of Jan-25) : -------- document.writeln('<th nowrap><font FACE="Verdana, Arial, Helvetica" SIZE="1" color="#000000">SEARCH&nbsp;&nbsp;</font></td>'); -------- (note: I've edited a little leading whitespace out from the original line). If you instead match the <th> with a </th> (or alternatively <td></td>) then the page (table) lays out correctly.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Not fixed on 1/25 build. Will check on next build.
Status: RESOLVED → VERIFIED
verified with Jan.27 build
Looked at the 1/27 build on Win 95. The number 3) issue still exists. Paul, please take a look and see if that's true.
You need to log in before you can comment on or make changes to this bug.