18671 - Browser displays only a partial page

Status: VERIFIED WORKSFORME

(SeaMonkey :: General, defect, P3)

Description

[mward]

* TITLE/SUMMARY
Mozilla homepage (as well as most other webpages) finishe loading with only partial page displayed.

* STEPS TO REPRODUCE
0) Launch Viewer
1) Load http://www.mozilla.org/

Here are my specs:
Mac OS 9
Blue and White G3 350mhz
256mb Ram - Virtual Memory enabled

Using nightly build for 11/10/99 of mozilla-mac-M12
Prefered Memory size for Apprunner 5.0m11 Gecko set to 20000k

The problem is that when attempting to view most websites, the browser only downloads and displays small portions of the page and
usually leaves out all the body copy.  In the case of the Mozilla homepage, the browser only displays the Mozilla banner graphic at the
top of the page and the menu listings such as "At a Glance", "Feedback", "Get Involved", etc.  The rest of the page is blank, no text.  It
appears as if the browser loads the first two portions and then decides there is nothing more to view.  Oddly enough, as I click thru
the menu listings for the homepage, most of the links also load only partial pages except for "Feedback" and  "License terms" which
load full pages.  The browser does not freeze or lock, it just completes the page display without displaying the full contents of the
page.

This problem also effects most other pages.  Some other examples include:
http://www.macosrumors.com/
http://www.macsurfer.com/
http://macweek.zdnet.com/

I have given the preferences a thorough going over and have noticed the browser's "Appearance" preference could be the problem.
Where the sub-category of "Colors" is concerned, the "Text" and "Links" colors are defaulted to white and the browser's color picker
will not allow me to choose any other color.  The browser color selection pallet opens but it is not possible to select a new color for
the text or links.  I have deselected the option to always use my colors rather than the colors indicated for each specific webpage, but
this has not solved the problem.

Good luck and Thanks for the hard work you're doing, we're all looking forward to a finished product.

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

The browser works better than this for most people.  Is there anything peculiar
about your configuration that could be causing this?

Comment 2

[Eli Goldberg]

Reassigning all of leger's unscreened Browser-General bugs to [e-mail]
for pre-screening and triage.

Comment 3

[John Morrison]

I can't reproduce this with a current build on WinNT (1999122208). I'm hesitant
to mark this WORKSFORME, as this was reported on Mac. However, a lot of changes
in incremental display have occurred between 11/12 and today.

[e-mail] : can you try this again with the M12 build? Thanks.

Comment 4

[Sean Richardson]

Wasn't there a bug for a while back in November where one byte was being lost
from each chunk processed by the parser after the first? Bug 19337. That could
certainly explain something like this, if the missing byte was a "<" or ">" .

But this definitely needs retesting on a newer build on a Mac.

Comment 5

[Myk Melez [:myk] [@mykmelez]]

Set QA Contact to Eli ([e-mail]) for verification on recent Mac build
and sent the following email to the reporter:

-----
Hi,

You submitted bug 18671 to Bugzilla.

http://bugzilla.mozilla.org/show_bug.cgi?id=18671

The consensus of the people who have looked at the bug is that you should try
again with one of the later builds, since many things that may affect this bug
have changed since the build with which you experienced it.  Download the latest
build at the following URL:

ftp://ftp.mozilla.org/pub/mozilla/nightly/2000-01-04-09-M13/

If you still see the bug in the latest build, go to the bug at the above url and
add a comment about it.  That will set the wheels in motion to take a closer
look at this bug and try to resolve it for you.

Myk
(volunteer bug hunter)
-----

Comment 6

[Eli Goldberg]

Hmm...I can't reproduce this at all using the 200010409 build on Mac OS, with
information provided in bug report, and am resolving as WORKSFORME.

[e-mail]: as myk said, if you're still seeing this on a current build,
please re-open with your comments. Thanks!

Comment 7

[Eli Goldberg]

No follow-up from reporter after one week; rubber-stamping as Verified/WORKSFORME.