Closed Bug 16582 Opened 25 years ago Closed 25 years ago

repeating content for large pages

Categories

(Core Graveyard :: Tracking, defect, P3)

PowerPC
Mac System 8.6

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: petter.sundlof, Assigned: harishd)

References

()

Details

I've discussed this with "shaver" a bit, and it seems to be Mac OS specific, and
more specifically, specific to local files.

When rendering large pages, like 20+ KB, it at some point repeats the content,
breaking the document somewhere and starting from the top. It doesn't loop, it
just renders it an entire time and it ends.

Let me illustrate

The page looks like this in Netscape 4.x:

A)Start
B
C
D
E
F
G
H)End

And in Mozilla (M11, 1999-10-14-11, and older ones):

A)Start
B
C
D
A)Starts from top, breaking in the middle.
B
C
D
E
F
G
H)End

If I for example have Javascript at the top, it works only on the second,
repeating part.

I've checked if it has something to do with my HTML, but it doesn't. I replaced
all HTML that could matter with plain text, but it still occurred.
Assignee: chofmann → rickg
parsing problem?
I do not understand what you mean by "parsing problem".
Assignee: rickg → harishd
Can you try tracking this down please?
odd@findus.dhs.org, could you please give me a reduced case to reproduce the
problem.  Because I'm not seeing the repeat problem.
Sorry if I didn't say this - but it's most likely a MAC-specific bug. I talked to

shaver@netscape.com about this.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified with Mac 8.6 and Mac 9.0 both load fine.

FYI: Tested with Oct. 19th build.

Marking bug WORKSFORME.
Well, guess I'll just skip it. Might check back when I've tried a build => 19

oct.
Marking Verified as WorksForMe per above comments.  Please use latest nightly 
build from: http://www.mozilla.org/binaries.html and reopen bug if is happens 
again.  Thanks!
Status: RESOLVED → VERIFIED
Summary: repeating content for large pages
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.