Opera Admits @Font-Face Bugs In Opera 10

Sep 30, 2009

For sheer balls, you have to admire Opera’s CTO Håkon Wium Lie. Over the past couple of years he has: 1) filed an antitrust complaint with the EU against Microsoft for it’s failure to support “fundamental and open web standards” in Internet Explorer 2) addressed a group of professional font designers and advised them to, essentially, give away their work for free 3) publicly accused Microsoft of having a monopoly on fonts 4) written an article about font-linking for a major web design publication without a single mention of licensing issues.

The Fat Lady Farts

After all the noise, Opera goes and gets @font-face wrong.
We recently reported Opera’s non-standard @font-face syntax, but apparently the problems go deeper than that.
They’ve owned up to it on their developer website:

Opera's Apology On Their Developer Website

Opera's Apology On Their Developer Website

A demo page showing the problem here: Web Fonts Problem

A demo page showing the hack for fixing here: Web Fonts Workaround

Of all the things to screw up on, it had to be @font-face, of course.
Ouch! That’s gotta hurt.

In keeping with Opera’s new schizophrenic marketing motto: “Follow The Standards. Break The Rules”

Due to a bug in Opera 10, specifying different weights and styles for a single font-family name currently breaks — only the last font specified (typically a bold/italic font) is applied, overriding other weights and styles of that font family. We are already working on a fix, which will be rolled out via our auto-update mechanism soon — in the meantime, you can avoid this issue by defining bolds and italics as different font families, and applying them explicitly on the elements you want to use them for. Of course, this workaround will continue working even after we’ve fixed the problem in question.

So, to put it another way, “Yeah, we know we screwed up, but it’s no big deal, really, because

Seven Web Fonts Showcases
svg fonts

Sharing Options:

Leave a Comment

Previous post:

Next post: