Closed
Bug 200935
Opened 21 years ago
Closed 21 years ago
blank space instead of content
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
INVALID
People
(Reporter: ihok, Unassigned)
References
()
Details
(Keywords: perf)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 It's hard to describe visually what exactly is wrong, but you can tell that it's wrong. Briefly, 1.3 fails to render the content of the page, possibly due to the size of the page, and the vertical scrollbar grows out of all proportion to the actual document. Sorry, don't have time to analyze this right now. Looks fine in IE6. Reproducible: Always Steps to Reproduce: 1. Go to http://www.bbsinc.com/iso8859.html 2. Look at in in Moz 1.3 3. Look at it in IE6.
Comment 1•21 years ago
|
||
WorksForMe, Moz 1.4a on WinXP. Looked more or less the same as with IE6
Comment 2•21 years ago
|
||
ok... i'm seeing the delayed loading of the right hand content as well... but I don't know if its a bug, or a perf issue, of just the facts of life due to all the included 3rd party scripts writing tables of unknown dimensions in the very tall left column... OS X 2003040608
Comment 3•21 years ago
|
||
-> invalid The whole page is a two column table. The left column contains many <script> referencing external js files. Mozilla has to wait for these files to load before it proceed. So it takes a lot of time for it to get through all the Ads before the real meat on 2nd column. On a related note, for some reason my computer can't see rcm.amazon.com (the host of the frame ads and script) (e.g. "ping rcm.amazon.com" returns "unknown host") but MSIE in AOL can. When I load the URL, I see in the status bar Mozilla at least try the server three times. Shouldn't it just give up after 1st try?
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 4•21 years ago
|
||
bug 200994 filed
Reporter | ||
Comment 5•21 years ago
|
||
(I'm the reporter.) Confirming that this is invalid. Regardless of stolenclover's technical analysis, the page now loads fine.
You need to log in
before you can comment on or make changes to this bug.
Description
•