Opera Border Radius in 2010?

Opera has been maybe the most stan­dards-con­scious brows­er over its life­time. This has result­ed in frus­tra­tion among users, who believe it to be “bro­ken” because it doesn’t ren­der lazy code cor­rect­ly — code that takes advan­tage of the for­give­ness of oth­er browsers, allow­ing you to write slop­pi­ly and get away with it.

But it has also result­ed in frus­tra­tion among web devel­op­ers, who are impa­tient at Opera’s reluc­tance to adopt any stan­dards that haven’t been laser-etched into plat­inum tablets down in the W3C’s base­ment foundry. Among them is the bor­der-radius prop­er­ty, an effect that will prob­a­bly be out of vogue any­way by the time Opera’s Presto engine imple­ments it. Of course, since CSS3 has been kicked around the W3C offices since 1999, and bor­der-radius itself since 2001, most oth­er engines (Gecko, WebKit, KHTML) stopped wait­ing and began invent­ing their own prop­er­ties for this effect. Presto has not.

In the course of remind­ing myself of this lam­en­ta­ble fact by search­ing for workarounds today, I noticed that some Opera devel­op­ers are casu­al­ly drop­ping hints that the full-blown, unqual­i­fied, W3C-craft­ed bor­der-radius itself has made an appear­ance in Presto 2.3, and that the next ver­sion of Opera will be pow­ered by 2.4.

It’s all true, I saw it on Twit­ter.