Comments on: How well do browsers support CSS Selectors?

By: guru

guru — Tue, 02 Sep 2008 14:51:44 +0000

On Opera 9.51 on WinXP
From the 43 selectors 43 have passed, 0 are buggy and 0 are unsupported (Passed 578 out of 578 tests)

Same machine, IE 7.0.5730.13
From the 43 selectors 13 have passed, 4 are buggy and 26 are unsupported (Passed 330 out of 578 tests)

Same machine, Firefox 3.0.1
From the 43 selectors 36 have passed, 0 are buggy and 7 are unsupported (Passed 373 out of 578 tests)

Same machine, Safari 3.1.2 (525.21)
From the 43 selectors 43 have passed, 0 are buggy and 0 are unsupported (Passed 578 out of 578 tests)

By: wodka

wodka — Fri, 29 Jun 2007 18:39:01 +0000

First of all the idea of the test, and the test itself is great! I’ve found it while looking for a solution for my problem in IE, i wanted to use the #id.class selector syntax.

So my question is, that is it possible to add #id.class, and .class1.class2 testing to the test?

By: Yeggstry

Yeggstry — Mon, 22 Jan 2007 04:37:34 +0000

Just so you guys know, I’m using the latest Firefox 3.0 Nightlies and got the following from the test:

From the 43 selectors 32 have passed, 4 are buggy and 7 are unsupported (Passed 369 out of 578 tests)

Look likes its getting better, and its only a pre-alpha 2 :)

Also it passes the ACID 2 test.

Thanks for the blog and links to the css3.info site, I’m in the process of rewriting my site to use some of these CSS3 styles that you have explained so well :)

By: Sonic

Sonic — Wed, 13 Dec 2006 21:56:25 +0000

Note that xhtml must use lower case, so the case sensitive comparison of ie7 could be acceptable.

By the way, anyone know a links to a table of comparison between crosbrowser support of css, updated to ie7 and ff2?

By: rakaz

rakaz — Tue, 17 Oct 2006 04:32:24 +0000

Hi Thomas,

We updated the test yesterday. It now has even more test cases and the result are a bit more refined. Read about it here: http://www.css3.info/blog/c...

By: Anne van Kesteren

Anne van Kesteren — Tue, 17 Oct 2006 04:23:29 +0000

Yeah, I wonder if that’s really what browsers do, but I suppose that’s what HTML4 says. You could be right though, I don’t really recall.

By the way, the reason Opera fails several attribute matching test is because we store the values known attributes in a special way which happens to be identical to the selector that shouldn’t match…

By: Thomas

Thomas — Tue, 17 Oct 2006 03:42:35 +0000

I just did the test with Opera 9.02 (build 8585), and the result was different from yours:

“From the 43 selectors 25 have passed, 3 are buggy and 15 are unsupported (Passed 346 out of 578 tests)”

By: rakaz

rakaz — Mon, 16 Oct 2006 06:47:46 +0000

Hi Anne,

Actually this is not completely true... It is a bit more complicated than the current testcase shows, the next update (later today) will solve that.

Whether or not an attribute should be compared using a case-sensitive or a case-insensitive method is determined by the HTML specification. Some attributes are marked as case-insensitive, for example: align. Some are marked as case-sensitive, for example: title and id. Some are case-neutral, for example: width. And other are not defined at all, but depend on the value itself, for example: href. To be on the safe side, these should also be compared in a case-sensitive way.

Basically, the browser needs to have a list of attributes. And based on that list it needs to determine what to do with which attribute.

By: Anne van Kesteren

Anne van Kesteren — Mon, 16 Oct 2006 05:11:29 +0000

You can see in the DOM inspector of Firefox for instance that several values are made lowercase. (Like LEFT for align=”" attribute.)

By: Anne van Kesteren

Anne van Kesteren — Mon, 16 Oct 2006 05:06:31 +0000

What Konquerer and other browsers do is correct. You should compare case sensitive there. Just the attribute name itself should not be a case sensitive match.