[4.x] Malformed table page lays out different than in Nav

VERIFIED FIXED in M14

Status

()

Core
HTML: Parser
P3
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: cheehoo, Assigned: harishd)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

19 years ago
mozilla does not load the following page correctly...
www.developer.com

I'm
using build 1999121208

Updated

19 years ago
Assignee: karnaze → pollmann

Comment 1

19 years ago
Reassigning to Eric.

Comment 2

19 years ago
It appears that the footer at the bottom of the page is displaying at the top
and to the right of the rest of the document.  This is inside a
<table><tr><td>.  Don't know why it is layout out this way, reducing the test
case...

Updated

19 years ago
Assignee: pollmann → harishd
Component: HTMLFrames → Parser
OS: Windows NT → All
Hardware: PC → All
Summary: Display Error → [4.x] Malformed table page lays out different than in Nav

Comment 3

19 years ago
This page gives new meaning to the words "malformed html".
I managed to reduce this a bit, attaching.

The root of the problem appears to be a missing <td> (one in particular, there
were many).  This page will probably need some parser changes to lay out like
Nav lays it out in addition to possibly some table changes.  Passing to Harish
first to look at the parse output.

Note that the footer row ends up contained in the main body row, which causes
the cell inside to lay out in the same row as the body rather than a new row
below it.

Comment 4

19 years ago
Created attachment 3480 [details]
reduced test case

Comment 5

19 years ago
This is crashing in savedtokens.

Updated

19 years ago
Target Milestone: M14

Comment 6

19 years ago
Setting milestone.
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 7

19 years ago
This problem should be FIXED by now.  Marking bug fixed.

Comment 8

19 years ago
Fixed in the Jan 20 th build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.