Opera has been maybe the most standards-conscious browser over its lifetime. This has resulted in frustration among users, who believe it to be “broken” because it doesn’t render lazy code correctly — code that takes advantage of the forgiveness of other browsers, allowing you to write sloppily and get away with it.
But it has also resulted in frustration among web developers, who are impatient at Opera’s reluctance to adopt any standards that haven’t been laser-etched into platinum tablets down in the W3C’s basement foundry. Among them is the border-radius property, an effect that will probably be out of vogue anyway by the time Opera’s Presto engine implements it. Of course, since CSS3 has been kicked around the W3C offices since 1999, and border-radius itself since 2001, most other engines (Gecko, WebKit, KHTML) stopped waiting and began inventing their own properties for this effect. Presto has not.
In the course of reminding myself of this lamentable fact by searching for workarounds today, I noticed that some Opera developers are casually dropping hints that the full-blown, unqualified, W3C-crafted border-radius itself has made an appearance in Presto 2.3, and that the next version of Opera will be powered by 2.4.
It’s all true, I saw it on Twitter.