261757 - on this large web page (html is 1MB) the page is not displayed correctly in areas

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Mime Čuvalo]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803

Whether because the webpage size is abnormally larger than usual or because of
another problem, the browser tends to garble up some of the html in areas
leaving (), |, or (!) behind.  I have seen this problem in Mozilla 1.7.2 and in
Firefox 1.0PR.  If it helps any, I have 240MB RAM and a 2.8 GHz processor.

Reproducible: Always
Steps to Reproduce:
1. Visit http://boingboing.net/2004_08_01_archive.html
2. Scroll through the page and you will see 'patches' of this problem.
3. In between articles you will see () on a line by itself followed by | on a
line by itself followed by a new article

Comment 1

[Hermann Schwab]

Attachment: 9 kb image of end of page showing (), |, or (!)

(), |, or (!) corresponds to some code not rendered, will follow in next
attachment.

Comment 2

[Hermann Schwab]

Attachment: code shown in previous attached image, 3 kb

this is the code of the image:
<span class="rss:item"> <a name="014049">
<b>Futurismic's new fiction from a Campbell nominee</b>
<br>
Futurismic is a group blog....

The <span> doesn´t have a corresponding </span>
<b>...</b> isn´t rendered
<blockquote>...<blockquote> isn´t rendered

and there you can find ():
<a href="http://www.futurismic.com/fiction/benno.html">Link</a>

(<i>Thanks, <a href="http://www.futurismic.com/">Jeremy</a>!</i>)


Seems related to 
Bug 58917 [FIX] No rendering after tag nesting/TAGVL has been exceeded

Comment 3

[Hermann Schwab]

Attachment: screenshot of region overlayed with vertical stripes, 77 kb

I´ve seen this at huge pages before, after scrolling down a lot the normal
rendering of the page is overlayed with vertical stripes. None seems to be
missing, only stripes added.
I tested this page on an Athlon XP1600+, 480MB RAM, (+32MB for nForce
integrated grafics), Win98SE, DSL
and on a Celeron333, 96MB, 8 MB noname grafics, 64.000bps ISDN
Both were showing the stripes at same places.
The stripes are shown (roughly guessed) in vertically equal sized parts of the
page, so 1st part non-striped, 2nd part striped, 3rd part non-striped, 4th part
striped, 5th part (smaller, as the page ends) non-striped.

Comment 4

[Hermann Schwab]

Attachment: end of 1st striped part, 11kb screenshot

here it ends, if you want to compare

Comment 5

[Hermann Schwab]

Attachment: start of 2nd striped part, 13 kb png

search for FELZ, if you want to find it in the page, or in the code

Comment 6

[Hermann Schwab]

See for similar issues
Bug 240560 Crash when I attempt to browse above URL or view yenc files
http://leo.typepad.com/tlr/2004/04/end_of_line.html

Start reading Bug 240560 comment 10, as a lot of previous comments had been
about  use of talkback.

Both websites are using ECTO, http://www.kung-foo.tv/ecto/

Validator:
http://validator.w3.org/check?uri=http%3A%2F%2Fboingboing.net%2F2004_08_01_archive.html&charset=%28detect+automatically%29&doctype=Inline&verbose=1
Sorry, I am unable to validate this document because on lines 11309, 11316-11317
 it contained one or more bytes that I cannot interpret as utf-8 (in other
words, the bytes found are not valid values in the specified Character Encoding).

Validator with encoding set to iso-8859-1 gives more than 8000 bugs:
http://validator.w3.org/check?uri=http%3A%2F%2Fboingboing.net%2F2004_08_01_archive.html&charset=iso-8859-1&doctype=Inline&verbose=1

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.