I've just downloaded KM to test a page with a lot of js on it.

FF, Chrome & Safari, IE8, Opera all render accurately and with acceptable speed. Also Mac browsers.

However, with KM the rendering is unbelievably slow, and the css misses in one important respect: two classes of ":after" have relative positioning which is ignored.

I might be able to do something about the css, but can anyone shed light on why the rendering... even before any js is implemented.. is so slow?

http://www-personal.usyd.edu.au/~ctillam/Changes/changes.htm

mouseover "welcome"...3-4 seconds.

Cheers.

K-Meleon 1.6 (currently alpha stage) has much faster js engine than 1.5. The difference in rendering speed in fovour of 1.6 is significant.

Quote
ctoz
I've just downloaded KM to test a page with a lot of js on it.

FF, Chrome & Safari, IE8, Opera all render accurately and with acceptable speed. Also Mac browsers.

However, with KM the rendering is unbelievably slow, and the css misses in one important respect: two classes of ":after" have relative positioning which is ignored.

I might be able to do something about the css, but can anyone shed light on why the rendering... even before any js is implemented.. is so slow?

http://www-personal.usyd.edu.au/~ctillam/Changes/changes.htm

mouseover "welcome"...3-4 seconds.

Cheers.

1.) Firefox 3, ... have new JS engines with JITs.

Official K-Meleon has GRE that is contemporary to Firefox 2.
That has a slower JavaScript engine.

A look into 1.5.4's error console shows that GRE 1.8 does not know all css You used.
9 errors - does not know, leaves line out.

These 9 are not with GRE 1.9 based K-Meleon1.6a3.

I assume that 1.5 slows on the errors. & it cannot do what it does not know.


2.) The reason why 1.5. is slower is probably not in Your css (which is only twice the size I use on my Home page) but in changes.js.



Edited 1 time(s). Last edit at 04/06/2010 02:19PM by guenter.

Thanks, I'll check the newer version.

The CSS errors are prolly the alternates directed at Safari & Chrome.

One thing tho: the page renders from bottom right upwards: is this standard for all browsers?

1.6 is ok on speed and CSS. phew!.

Anyone out there with IE6 to test same page?

cheers

I got the page is 2.391 seconds with 1.6.0a3 version with js off and 5.032 seconds with js on.

5.032 ain't so good.

I'm looking at ways to lighten the scipting: there's still a lot of script and content to come.

Quote
ctoz
Anyone out there with IE6 to test same page?

You can try to use "Multiple IE".

It is not supported any more - but maybe You can combine the idea with using an IE shell to get the different Trident engines going on Vista or Win7.



Edited 1 time(s). Last edit at 04/07/2010 03:52AM by guenter.

Quote

not supported any more

... yebbut, still about 10% of users although most may be on office intranets.

Is it common practice to compensate for IE6 these days?

"Multiple IE" as IE6 crashes or freezes: and I'm on XP sp3 so it should be ok.

I'll hunt elsewhere for a victim. Cheers.