> OK. So it can work if every browser that supports the format puts in in > Accept: as soon as it begins support. That may be true of WebP; I don't > believe it's true of WOFF. Is it? > > you need to opt-in to the transcoding, yes. But you make it sound like you can't use woff at all without transcoding, and that's not true. Doing the right http thing doesn't interfere with also doing the right css thing. Indeed we've been using woff with that crazy text/xml header - just changing it to reflect our true preferences enables both scenarios. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
- Re: Intent to implement: WOFF2 web... Patrick McManus
- Re: Intent to implement: WOFF2 web... Jonathan Kew
- Re: Intent to implement: WOFF2 web... Patrick McManus
- Re: Intent to implement: WOFF2 web... Anne van Kesteren
- Re: Intent to implement: WOFF2 web... Patrick McManus
- Re: Intent to implement: WOFF2 web... Jonathan Kew
- Re: Intent to implement: WOFF2 web... Patrick McManus
- Re: Intent to implement: WOFF2 web... Robert Kaiser
- Re: Intent to implement: WOFF2 web... Jonas Sicking
- Re: Intent to implement: WOFF2 web... Gervase Markham
- Re: Intent to implement: WOFF2 web... Patrick McManus
- Re: Intent to implement: WOFF2 webfont format chris
- Re: Intent to implement: WOFF2 webfont format Ilya Grigorik