Probably more noticeable on slow servers or slow connections:

When a page is loading it is drawn at the same time. That's normal and okay.

When all bits of the page have finally been transfered K-M refreshes the complete page (just like on a reload, but quicker).

That shouldn't be necessary and K-M didn't to that in previous betas (or 0.8 releases IIRC). Its a bit like flickering, just when the page finished loading and it is annoying.

What do others think?

I noticed the behavior with beta 3(or one of the later test builds), but I didn't know if it was something on my end. I haven't noticed it yet on beta 4.

IIRC it wasn't in the original beta 3, but it first appeared in later builds (end of Nov / beginning of Dec.?).

It doesn't happen every time, but still too often. ;-(

Yeah, I noticed the flickering on beta 4 too, which I didn't see on beta 3. Exactly like ra described, it seems to quickly refresh after the page is done loading.

I can't explain it, but the flickering has stopped...

Not sure if this is applicable, but I had this same problem with beta 3 in W95 until I did something that I eventually have recourse to do when testing betas: I cleaned up the Registry.

Of course the usual cautions apply, i.e. if you don't know how to backup your Registry and how to restore from said backup if your Windows gets hosed, it's best not to embark on this. But for what it is worth, here's what I did:

First I ran Microsoft's RegClean and gave it free reign to clean as it saw fit.

Then I used another product, RegSeeker, to track down any K-Meleon 0.8.2 (I've been so happy with 0.9 beta 3 that I uninstalled it) and 0.9 beta 2 entries extant and deleted those.

Rebooted and K-Meleon 0.9 beta 3 runs like a champ with no extra refresh, even seems to render web pages quicker than before the cleanup .

Ra,

Have you seen this in RC1 at all?

Andrew,

Have DSL.
I think I have seen this in every official beta including RC1, and Bleading.
It does not always happen.
I thought I had posted about this already.
Will look for my notes later.

I usually see the problem in these forums.
The HTML for these forums has some problems.
"<style tpe="text/css">" instead of
"<style type="text/css">"
<style*</style> outside head.
Missing doctype etc.
Could there be a problem with the way the betas handle the errors?
Perhaps there is an option to turn off redraw after error?
I have tried to correct the errors with Proxomitron.
My modifications to the HTML did not fix the problem.
I could be missing something.
What would be the correct doctype? Or is there one?

I do not remember seeing this in the beta Fast Sjonny offered.
Didn't he use his own chrome? Could that matter?
He also modified the prefs.
Is that beta still available?

When I checked with Firefox, I could not see the problem.
But it does not always happen.

Test to see if you see this in the MFCEmbed browser that's in the base K-Meleon directory.

MFCEmbed browser has same problem.
I think the video driver and resolution has something to do with it.
It most often happens on the 1024x768 laptop.
Also, wide forum pages seem to be more susceptible.

The beta Fast Sjonny offered and Wechselbalg had this too,
have checked notes.

Interesting, I couldn't duplicate it in MFCEmbed. But that's my exact setup where I'm seeing it - 1024 x 768 on a laptop, FWIW.

Anyone running Mozilla 1.7.5? We should see if it affects that as well.

"1024 x 768 on a laptop"
Toshiba?

"Interesting, I couldn't duplicate it in MFCEmbed."
Try opening links in new windows.
My 800x600 laptop ran quite well with MFCEmbed.
I saw the problem only once while using it and the refresh was in a new window. The link, opened from the "General" forum, was either
http://kmeleonbrowser.org/forum/read.php?f=1&i=20619&t=20619
or
http://kmeleonbrowser.org/forum/read.php?f=1&i=17422&t=17422

On pages that I would expect RC1 to possibly show this behavior Firefoxmoox may start with a blank page, hold it blank for a while, and then draw it without any hiccups. I do not care for that either.
Choose your poison, eh?

Andrew,

Have you seen this in RC1 at all?

IIRC yes and I'm currently getting it with 0.9 RC2 (default setup).

The strange thing is that it stopped at some point in the past. I was only getting it the first few hours or days after installing the new version. I have a guess, but it's only a guess: When the cache is full K-M won't flicker anymore (or only in 1 out of a 1000 times). That's the only explanation I can think of and I bet RC2 will stop refreshing in a few days, just like the previous versions did (I don't think that changing cache comparison from automatically to always makes a difference, but as I prefer always I will change it now...).

Okay, just got it again on the K-M homepage (but the logo was just loading) with cache comparison set to always. But my guess is still there. We'll see...

ra,

You're on RC2 now, right?

I think I've seen it at least once on RC2. Not as often it seems but still there.

Andrew,

yes, please read the post above my last one, too. :-)