Closed Bug 1489 Opened 26 years ago Closed 26 years ago

"freshmeat" tables intensive page takes a very long time to layout

Categories

(Core :: Layout: Tables, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED DUPLICATE of bug 985

People

(Reporter: angus, Assigned: buster)

References

()

Details

This page took me about a minute to load. I'm using 11/21/98 4:00pm debug bits. Throughout the loading of this page, I see messages like this in stdout: 61 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61 Body(TD)(0)@00FAEB10: bad parent: maxSize WAS 135,149475 Body(TD)(2)@0193B870: bad parent: maxSize WAS 3201,149475 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61 Body(TD)(0)@00FAEB10: bad parent: maxSize WAS 135,149850 Body(TD)(2)@0193B870: bad parent: maxSize WAS 3201,149850 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61 Body(TD)(0)@00FAEB10: bad parent: maxSize WAS 135,150225 Body(TD)(2)@0193B870: bad parent: maxSize WAS 3201,150225 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61 WARNING: cell Body(TD)(1) content returned desired width 1305 given avail width 61
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
It's not Steve's fault. The problem is that the page has 37 images without width/height tags. When we get the image sizes we generate reflow commands. Because the block/inline code hasn't yet been optimized for incremental reflow we basically reflow all of the frames for each reflow command. That slows things down by like a factor like 37 *** This bug has been marked as a duplicate of 985 ***
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.