Opera 9.5 races ahead with CSS 3 support
Opera have just announced version 9.5 of their desktop browser, currently codenamed ‘Kestrel’ - and as you can see from the screenshot they’ve chosen, it passes the CSS 3 selectors test with flying colours!
They mention that CSS 3 support will be improved (text-shadow is provided as an example), as well as superior SVG support
, and a new Javascript engine will allow better access to websites with wonky coding.
This sounds like a really exciting release, and should give Opera the accolade of being the most CSS 3 compliant cross-platform browser. Weekly builds will be available shortly.
I hope this serves as an inspiration for the teams behind Firefox, Safari, and Konqueror to improve their CSS 3 support. This’ll kind of competition is what makes things happen. If it’s good enough, then it might even get MS to make IE more CSS 3 compliant.
Konqueror already has the best existing CSS 3 selectors support, but it would be great to see them support a few more declarations; multiple backgrounds and columns, for example.
Have not Opera been the superior CSS 3 browser for some time all ready? Or where Konqueror better?
Konqueror is the only browser to currently pass the CSS 3 selectors test with no errors.
Konqueror 3.5.7 passes all tests. Anyway Opera is the best and will be better. :)
Actually, even konqueror 3.5.6 passes perfectly, and it’s been out since 25. January.
On CSS3 selectors, Opera is clearly in the lead. But for CSS3 generally, Safari 3/WebKit is far ahead of the pack. Of the 19 CSS3 styles previewed on this website, Safari 3/WebKit has implemented 17. Sounds like Opera 9.5 will increase its score, but likely FIrefox will remain in second place with 8 styles implemented. As of Opera 9.2, Opera had 4 styles done.
Not that anyone’s counting, of course… And where is IE, anyway? :-)
Hold up a minute, I forgot to include the subject of this blog’s article! Attribute selectors! Including selectors, the score is: Safari, 18; Firefox, 9; Opera, 5.
Leland
P.S. I don’t intentionally exclude Konqueror… but implicitly include it since it’s cut from the same cloth as WebKit.
Sounds good, but the weakpoint still is its freaky interface, its no way natural on any plattform… Opera should seperate the renderingengine from the app, and a produce native app on every plattform. A windowsbrowser that feels like a windows app, a mac-browser that feels like a native cocoa app and of course one for the gnome/kde guys too.
a good example is camino, it brings the geogeous firefox rendering engine together with a typical osx interface. way to go. and say what you want about IE7 but it feels very vista-ish.
Thilo - This is from the announcement:
@Leland: KHTML and WebKit share a lot of code, but they’re absolutely NOT the same as far as CSS3 is concerned. The selectors test is passed completely by Konqueror, and not by Webkit / Safari 3, whereas WebKit supports other css3 features that Konqueror does not support.
“The selectors test is passed completely by Konqueror, and not by Webkit / Safari 3, whereas WebKit supports other css3 features that Konqueror does not support.”
Precisely why I included both Safari and Konqueror in my comment before; neither perfect selector support nor inclusion of every other feature possible is enough, but when a browser has both (which is what Opera seems to be attempting here), that browser raises the bar and forces its competition to keep up.