Opera have released version 9.5 of their browser today, and the good news for our readers (and web users in general) is that there are lots of CSS 3 features implemented. This article on dev.opera.com goes into more detail, but major improvements include:
- @media queries
- hsl colours
- overflow-x & overflow-y
- all css selectors
- form pseudo-classes
Download a copy today and take a look at some of the examples on our Preview pages. I’ve just noticed that the background-size example doesn’t work, but that seems to be our implementation at fault, not theirs.
You can skip to the end and leave a response.
So, no rgba/hsla after all?
Also, you forgot about the most important addition :not()
Possibly not, opacity applied to whole element, while color to text and other parts. How do rgba colored semitransparent borders must look for example? Fonts may have anti-aliasing including subpixel rendering and how do they must look semitransparent too?
Resolutions 2007-11-27 ( http://www.w3.org/blog/CSS/2007/11/29/resolutions_5 )
No official resolutions for 2007-11-27, but the CSS3 Backgrounds and Borders editors did agree to adopt Anne’s border-radius extended shorthand syntax proposal.
Resolutions 2007-09 Beijing Part IV: CSS3 Borders ( http://www.w3.org/blog/CSS/2007/09/25/beijing_part_4 )
Resolved: The border-radius shorthand shall take 1–4 values that set each of the four corners to circular radii, as in the -moz-border-radius shorthand. That is,
border-radius: TL TR BR BL;
border-radius: TL BL+TR BR;
border-radius: TL+BR TR+BL;
CSS Backgrounds and Borders Level 3: Issue 4 ( http://csswg.inkedblade.net/spec/css3-background#issue-4 )
the border-radius shorthand shall take up to four values that each set both radii for the corresponding corner as in Mozilla’s implementation. The first value applies to the top-left corner, and rest are assigned clockwise. Missing values are filled in as for margin et al. Adopt Anne’s proposal for extended syntax that allows setting elliptical curves.
Sounds ready enough?
HSLA and RGBA are not simple to add to our rendering engine as it sounds. They are supported post Core-2.1 (the engine in Opera 9.5) but didn’t make it in Core-2.1 as the fixes were too risky. By risky I mean there is too high risk of regressions for the time it was added to the engine – remember Opera (and to some extent WebKit) were adding things to pass Acid3 during our release cycle.
As Peter says border-radius wasn’t stable during our planning process. It is stabling off now, and we will most likely add it for the next version of the rendering engine, baring any unexpected changes.
This release feels quite rushed… As if they wanted Opera 9.5 to be released before Firefox 3 at all costs.
It’s a shame some nasty CSS bugs/regressions haven’t been fixed months after they’ve been reported, like the one you can see on this testcase: http://stifu.free.fr/dl/temp/opera-opacity-bug.html
[…] Impressively, the official release of the browser came only two days after the release of the Opera 9.50 Release Candidate build. For interesting facts about the release, you can check out the official announcement or the coverage at Opera Watch. The latter also has some additional coverage on the new skin change. Or, if you’re interested in the improvements made in Opera 9.5 on the CSS front, be sure to look at CSS3 . Info’s synopsis. […]
After using Opera 9.5 for a few days, I am quite happy with its performance. While a lot of people were really looking forward to Firefox 3, the Opera team released Opera 9.5 with much less noise and much more improvements.
Opera 9.5 scores 83/100 on t…