Closed Bug 243356 Opened 20 years ago Closed 16 years ago

The speed at which Composer renders a page has slowed from the last build I used.

Categories

(SeaMonkey :: Composer, defect)

x86
Windows XP
defect
Not set
trivial

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: boofy_bloke, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040510
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040510

First there's a white page, then it renders the page with links according to CSS
colours, then it re-renders the page with links all blue.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Depends on: 242823
boofy bloke:
Could this be a duplicate of bug 242856?
Please retest with a current nightly build (the parts causing this problem are
currently backed out)!
With Build ID 2004053108 the page now flashes white then renders with links in blue.
boofy bloke:
now what about this?
Does the latest 1.8a2 release work for you?
If not, please try with a new profile.
Product: Browser → Seamonkey
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/
I get the window frame (menus, bars, etc.), a flash of white in the window pane,
then the page is rendered completely.
(In reply to comment #5)
> I get the window frame (menus, bars, etc.), a flash of white in the window
> pane, then the page is rendered completely.

Matti

Anything wrong with that "intermediate step" of a blank page before the full page is rendered?  In the past, was there a time when this did not happen?

No signficant rendering delay for me with current trunk build 1.5* 
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060512 SeaMonkey/1.5a (and 20060101)

simple pages render instantaneous
http://www.mozilla.org/projects/seamonkey/start/
http://www3.lehigh.edu/

more complex page with tables has the symptoms you state, but still rendered within respectable 2 secs.
http://www3.lehigh.edu/campushome/default.asp

please cite a URL if this is still a problem for you
Severity: normal → trivial
I have to say that any delay in rendering a window is annoying at best; the longer it takes for a page to appear on the screen the more annoying it is (I reckon that SeaMonkey should appear on the screen before the "image" becomes active, but that's a story for another day).

If I have a page open in Composer then open a link from that page, going from the original background colour (eg black) to a flash of white then on to a different background colour (eg black) is visually disturbing. Ideally SM would read the background colour before drawing the new window.
Matti, do you still have this problem with SeaMonkey 1.1.9 or 2.0a1pre?

Have you any site for testing?

SeaMonkey 1.1.9 and 2.0a1pre
It rendering http://www.seamonkey-project.org/ fine for me.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
VERIFIED
Status: RESOLVED → VERIFIED
worksforme is the right solution without patch in the bug
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.