Opera and CSS3 support compared to the other browsers
Published August 21st, 2007 7:52 PM EDT By Daniel GoldmanAjaxian blogged about CSS3 support in browsers. So how do the major browsers compare with support for CSS 3?
“CSS 3 has been out there for quite some time, but apart from Opera, other browsers have selectively implemented their pet features.”
We’ve done a lot of work on CSS3 support lately. In the upcoming Opera 9.5 version of the desktop browser we have added full support for CSS3 selectors, as well as other CSS3 properties. (It sure helps to have the creator of CSS, Hakon Wium Lie, as the Chief Technology Officer (CTO) of Opera 
)
using
No hints as to what those other CSS 3 properties might be? No? Please…
using
while having complete support of css3 selectors can give that nice geeky warmth i wouldnt consider it important. it is important only in an artificial race between browsers. but in real webdevelopment there are parts of standards or ’standards’ that are far more important. like my pet property - overflow-x/-y. i know that these are FINALY in 9.5 but it is about 3 years too late. lots and lots of pages use these, and these pages looks BAD in opera. mostly ‘layout’ pages - like ajax apps mentioned in this very article.
lack of overflow-x/-y alone made making webApps for opera PITA. and why it is so bad? because people, who regardless developed for opera, got used to hacking opera with some js tweaks. these tweaks will break in 9.5 on lots of sites. OTOH developers who ignored opera problems will ignore them even with 9.5 support, because most of them will never look at opera again. lots of them, including some senior specialists are so deeply in love with firefox+firebug, that they dont use anything else + IE. they do wrong, but well..
opera is to blame here again - no developer tools for a LONG time, and when they finally arived, they were some sucky advanced bookmarklets put together, that realy couldnt compare to firebug, or even IEwebDeveloperToolbar. firefox has JS debugging with firebug, IE can debug it trough visual studio, how does opera debug JS? and dont you think, that JS is now more important than CSS?
but that is not so topic relevant. i would like to ask someone at opera - how you implemented the missing css features: the way other browsers do, or (as always) the way you think is the best, and because nobody agrees it could as well not be implemented at all? reading halvors blog i always got amazed how many problems opera causes to itself by always going upstream. IE could go upstream with 95% marketshare, opera with .95% marketshare should realy go with the flow, and resort to doing it better and faster.
btw. i think that post title is not really relevant to linked article, as it says very little about opera indeed:)
using
Opera 9.5?
It`s not exits, and never will be exists.
using
Looks like an “I don’t like where CSS is going” rant to me, not anything informative. I was expecting an actual comparison of which browsers have which CSS3 features.
So, any chance Opera might be adding rounded corners, box-shadow, or multiple backgrounds sometime soon? Please?
using
“how many problems opera causes to itself by always going upstream”
Examples?
using
preview build or it didn’t happen
using
Aside from CSS3 it would be nice if the text wrap problem evident most notably in Gmail and Wordpress post/email composition was fixed as a priority. This has been around for a while and is I would have thought for most users a far bigger issue than CSS3 support.
using
@Duncan: I just have red the “text wrap” and if I read it good they are already working on that problem. and probably will be fixed in the next big thing.
using
“It’s unlikely to be fixed until Peregrine (the next major release).” said Junyor, Opera employee
peregine is going to take several months to arrive, most probably more than a year or two analysing current opera development schedules.
so for a year or longer it is better to use something else than opera for gmail/vox. considering, that default wordpress theme is bugged in opera (top links not clickable in certain conditions) using opera for wordpress is tricky anyways. go here - http://www.favbrowser.com/why-firefox-is-blocked/#comments and see how the breadcrumb behaves after scrolling.
using
Yep, given the current schedule for kestrel (remember back in june when they said it was a few weeks away?) PEREGRINE == DUKE NUKEM FOREVER
using
@Berend: Yes I did read what I linked to! As others have said, peregrine is not going to be here any time soon. My point is simply that the average user I believe (imho) is going to be more interested in a bug fix like this being fast tracked than CSS3 support.
using
And what is it all useful for ? :]
using
@sid: Tim probably said that before Opera had planned Kestrel at all. Ignore “Peregrine” in that statement, what matters is “next major release”.
using
@joachimb Unfortunately, a “major release” almost always means an increase in the first digit of the version number, which in this case means a switch from 9 to 10 AKA Peregrine.
using
Why didn’t sid give us, say, five examples where Opera is “always going upstream”?
using
@Beeblebrox: Yup, almost. This is an exception.
using
Ping:
Why didn’t sid give us, say, five examples where Opera is “always going upstream”?
using
@sid: Howdy. I’m Junyor on the MyOpera forums. As Joachim already pointed out, that post was made prior to our plan to release Kestrel before Peregrine. In any case, the bug will be fixed in Kestrel.
using
Junyor, i stand corrected, and indeed VERY happy. that bug IS a killer. thanks for clarification
using
On the one side Opera works on CSS3 - and on the other side: look at the web, designers should work with CSS. But there are hundreds of thousands of sites doing layout with tables