Comments for jpsykes

Comment on Testing CSS Performance (pt 2) by jay7

jay7 — Tue, 13 May 2008 07:43:53 +0000

oh sorry for my messup, besser means better :)

Comment on Testing CSS Performance (pt 2) by jay7

jay7 — Tue, 13 May 2008 07:42:52 +0000

Hello,
interesting result you got there, but i also tested it with the webkit (r32945) and it seems the performace got a little bit besser. Result were about 3745ms / 2291 ms.

Comment on Testing CSS Performance (pt 2) by JP

JP — Mon, 12 May 2008 23:47:21 +0000

@jay, totally correct, my mistake for using the wrong term in the post, I’m going to go back and edit my references to that, thanks for the correction :-)

@jake, Jim and I are already compiling a number of other tests to run, I’ll add that to it, I’m also going to take Jay’s point above and test child selectors. :-)

Comment on Testing CSS Performance (pt 2) by Jay

Jay — Mon, 12 May 2008 22:13:34 +0000

Child selectors would be table>tr>td
table tr td are descendant selectors.

Comment on Testing CSS Performance (pt 2) by Jake Archibald

Jake Archibald — Mon, 12 May 2008 22:02:42 +0000

@JP: A td must always be within a tr which must always be within a table to be valid. If a td is placed outside a table does Firefox 3 implicitly create the table & tr in the DOM (like most browsers do with tbody)?

Firefox 3 may be using this rule to skip assertions.

I’d be interested in seeing the same test but using unrelated tags, such as “div p a.whatever”

Jake.

Comment on Testing CSS Performance (pt 2) by Performance web » Archive du blog » Gains de performance des sélecteurs CSS

Mon, 12 May 2008 21:40:45 +0000

[…] a été dans l’impossibilité de distinguer une quelconque différence. Il lui a fallu faire un second essai avec tableau de 20.000 cellules bourré d’identifiants et de classes, avec autant de […]

Comment on Testing CSS Performance by Performance web » Archive du blog » Gains de performance des sélecteurs CSS

Mon, 12 May 2008 20:24:49 +0000

[…] Je n’ai pas eu le courage de le faire, prévoyant des résultats peu concluants. Avec son premier essai il a été dans l’impossibilité de distinguer une quelconque différence. Il lui a fallu […]

Comment on Testing CSS Performance (pt 2) by JP

JP — Mon, 12 May 2008 20:15:29 +0000

@Chris, don’t get me wrong I’m not saying descendant selectors are bad and shouldn’t be used, more that they do seem to come with a price and it’s worth being aware of it if you need to be thinking about optimization of your code and speed of rendering.

Comment on Testing CSS Performance (pt 2) by JP

JP — Mon, 12 May 2008 20:02:05 +0000

Jake, yes indeed that flow seems to be the conclusion on most browsers.

I think for me, the biggest come away was how big the difference is in Safari 3 and how small it is in FF3, it makes me question whether FF3 is doing something the other browser makers aren’t.

Comment on Testing CSS Performance by Javascript News » Blog Archive » CSS Child Selector Performance

Javascript News » Blog Archive » CSS Child Selector Performance — Mon, 12 May 2008 19:08:20 +0000

[…] first one was rather a half-assed idea that afterwards seems fundamentally flawed as a […]