Comments on: CSS3 Selectors :last-child http://www.dtsn.co.uk/2008/04/14/css3-selectors-last-child/ Daniel Thomas Saxil-Nielsen Thu, 28 Aug 2008 10:44:03 +0000 http://wordpress.org/?v=2.6.1 By: Daniel http://www.dtsn.co.uk/2008/04/14/css3-selectors-last-child/#comment-513 Daniel Mon, 14 Apr 2008 18:09:24 +0000 http://www.dtsn.co.uk/?p=126#comment-513 Hi Jos, I totally agree with you, no one can seem to get this right, i wouldn't recommend anyone using the CSS3 structural pseudo-classes, unless they are using prototype (which supports them all). I just thought i would draw peoples attention to them, they are powerful, and maybe one day they will be fully cross-browser compatable. Hi Jos,

I totally agree with you, no one can seem to get this right, i wouldn’t recommend anyone using the CSS3 structural pseudo-classes, unless they are using prototype (which supports them all). I just thought i would draw peoples attention to them, they are powerful, and maybe one day they will be fully cross-browser compatable.

]]> By: Jos Hirth http://www.dtsn.co.uk/2008/04/14/css3-selectors-last-child/#comment-512 Jos Hirth Mon, 14 Apr 2008 17:41:33 +0000 http://www.dtsn.co.uk/?p=126#comment-512 Unfortunately :last-child (and all similar pseudo class selectors) are broken in Firefox for everything than the most simple kind of test cases. The reason for that is that those rules are applied whenever the page is drawn. This unfortunately includes partial still-loading renderings. And well, the final rendering step doesn't fix that. See: http://kaioa.com/node/39 Fortunately it's more usable over in Opera, but even Opera has some issues with that stuff if the DOM is manipulated via JS. Maybe Safari gets it right. Right now it isn't really usable even if you ignore IE completely. Unfortunately :last-child (and all similar pseudo class selectors) are broken in Firefox for everything than the most simple kind of test cases. The reason for that is that those rules are applied whenever the page is drawn. This unfortunately includes partial still-loading renderings. And well, the final rendering step doesn’t fix that.

See: http://kaioa.com/node/39

Fortunately it’s more usable over in Opera, but even Opera has some issues with that stuff if the DOM is manipulated via JS.

Maybe Safari gets it right. Right now it isn’t really usable even if you ignore IE completely.

]]>