Slashdot Mirror
Opera 9.5 To Fully Support CSS?
Albert Sandberg writes "According to a developer blog, it looks like Opera 9.5 (which has been code-named Kestrel) will be the first browser to fully support the CSS selector test (test is here). Finally! Weekly builds should start being available in a few weeks."
This post is fanboyism at its worst. Opera is going to fully support CSS selectors, not CSS. Selectors are just one structure in the CSS language. There are still many other parts of the CSS standard that are not supported by Opera and are not yet planned for any future release.
Right. Opera has been completely free since 2005.
Um, yeah... maybe you didn't get the memo, but Opera's been free of charge and advertisements for like 2 years now.
Maybe not
For the record...
Iceweasel 2.0.0.4
From the 43 selectors 26 have passed, 10 are buggy and 7 are unsupported (Passed 357 out of 578 tests)
Konqueror 3.5.7
From the 43 selectors 43 have passed, 0 are buggy and 0 are unsupported (Passed 578 out of 578 tests)
So konqueror (which I thought shared source with safari?) is 100% compliant at least as of version 3.5.7 (I don't have an earlier version to test.).
It stands for Cascading Style Sheets.
(That link was the first hit on google for a search on CSS, incidentally...)
It's official. Most of you are morons.
OK, fine. It stands for Cascading Style Sheets. Welcome to the Internets.
Spelling mistakes, grammatical errors, and stupid comments are intentional.
Very nice news but somehow not surprising by the constant underdog. It truly is a shame that Opera only has 2% of the market considering how great it is in comparison to its competitors regarding speed, features, innovation and security. Imagine a browser so great that people actually paid for it as late as 2005 (these days, Opera is 100% free).
Since 1999 or so, the preferred way of putting style on web pages ("how this part of looks") is not mixed into the content structure ("what kind of information this part contains"), but in a separate place, the style sheet.
The style sheet Selectors say what parts of a page must carry it associated style, e.g. 2nd level headers (selector) must be blue and use a 14 point, bold, sans serif font (style).
The CSS stylesheet standard allows lots of complex kinds of selectors, and so browsers used to support only a small subset of selectors.
Got Pike?
Part of the issue arises from the fact that much of browser rendering code is ancient. Much of the basic rendering pieces weren't built to handle some of the CSS properties. For instance, many advanced selectors break when you are dynamically adding content or changing/adding stylesheets.
Expect Internet Explorer to lag again unless they completely replace large parts of their HTML rendering engine for standard-compliant sites. There is simply too much legacy code running against the Internet Explorer control, unfortunately.
Firefox 2.0.0.4 on Windows Vista:
From the 43 selectors 26 have passed, 10 are buggy and 7 are unsupported (Passed 357 out of 578 tests)
Internet Explorer 7.0.6000.16473 on Windows Vista:
From the 43 selectors 13 have passed, 4 are buggy and 26 are unsupported (Passed 289 out of 534 tests)
Lynx 2.8.3dev17 on Windows Vista:
No JavaScript == No tests. :(
Opera 8.5 on Nintendo DS:
From the 43 selectors 14 have passed, 3 are buggy and 26 are unsupported (Passed 313 out of 578 tests)
Opera 9.1 on Nintendo Wii:
From the 43 selectors 30 have passed, 2 are buggy and 11 are unsupported (Passed 450 out of 578 tests)
Opera 9.21 on Windows Vista:
From the 43 selectors 25 have passed, 3 are buggy and 15 are unsupported (Passed 346 out of 578 tests)
Safari 3.0.1 Beta on Windows Vista:
From the 43 selectors 25 have passed, 9 are buggy and 9 are unsupported (Passed 346 out of 578 tests)
Oddly enough, the Wii with an OLDER Opera wins in the Most Completely Working category, while Firefox wins in the Most They At Least Tried category (least unsupported).
Konqueror 3.5.6 Results:
From the 43 selectors 43 have passed, 0 are buggy and 0 are unsupported (Passed 578 out of 578 tests)
This release of Konqueror has been their stable release since last January was supplanted by 3.5.7 last week. So Opera isn't the first. A stable released browser has been able to pass this test for at least 6 months. I don't know how 3.5.5 and before would have done on it.
All that said, Firefox tends to do better with the javascript heavy sites and has extensions I can't live without. If I were going to use something else it would probably be Konq though. When KDE4 comes out, Konq will be easily installed on Windows and OS X. That might get a bit more momentum behind it.
From the 43 selectors 10 have passed, 1 are buggy and 32 are unsupported (Passed 276 out of 578 tests)
.5%, So its cool that it will support it, but it doesn't do me any good.
IE6 still makes up for 40-45% of the users on the site I maintain for work. Opera is less than
In America we are imprisoned by our fear of them.
A quick check of the KDE changelogs shows that Konqueror was brought into compliance with the tests with the release of KDE 3.5.6. Linky.
3.5.6 was released in January.
The claim that Opera is first does not occur in the blog entry. It is probably something the submitter added.
http://bayimg.com/CabbmAabg
No, it's not. It's been flagged for "Last Call" since the end of 2005 and is still aways from full recommendation status. CSS 2.1 (farther along, but similarly mired) to date is patchily implemented by all — some moreso than others, for various reasons — so why should one expect full support for this CSS3 Working Draft?
(Some do say the W3C is a bit byzantine, and yes, they are cranky about it. You, too, can be the judge of that.)