Open Bug 625358 Opened 15 years ago Updated 3 years ago

Support font/ mime supertype for web fonts

Categories

(Core :: Layout: Text and Fonts, enhancement)

enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: beta, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b9pre) Gecko/20110108 Firefox/4.0b9pre Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b9pre) Gecko/20110108 Firefox/4.0b9pre Firefox currently accepts any mimetype for web font loaded via CSS. It can do better than that. See URL for a draft IETF proposal for font/ supertype support that has expired. I hope to be encouraging it out from expiry. The hope is that as the draft progresses, web developers will start to use the as-yet-unproposed proposed subtypes. Reproducible: Always
Component: General → Layout: Text
Product: Firefox → Core
QA Contact: general → layout.fonts-and-text
Discussing this on the newsgroups/mailing lists is a better way to solicit Mozilla dev feedback. https://lists.mozilla.org/listinfo Bugs are only read by a small fraction of possible interested parties.
(In reply to comment #1) > Discussing this on the newsgroups/mailing lists is a better way to solicit > Mozilla dev feedback. https://lists.mozilla.org/listinfo Bugs are only read by > a small fraction of possible interested parties. Mhmm, I’ve sent off a few emails, this is just a tracker so far
The W3C WebFonts WG discussed this late last year, and the current position is that it seems unlikely a new font/ top-level type will be registered in the foreseeable future. See the email thread "WOFF type registration" at http://lists.w3.org/Archives/Public/public-webfonts-wg/2010Nov/. At this point, the expectation is that WOFF fonts will use application/font-woff (see http://www.ietf.org/mail-archive/web/ietf-types/current/msg01115.html); other font formats could potentially be registered similarly, though I don't know of anyone pursuing this at present.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.