On Monday 2018-03-19 22:32 +0000, Jonathan Kew wrote:
> As of this week, for the mozilla-61 cycle, I plan to turn support for
> OpenType Font Variations on by default.
> 
> It has been developed behind the layout.css.font-variations.enabled and
> gfx.downloadable_fonts.keep_variation_tables preferences.
> 
> Other UAs shipping this or intending to ship it include:
>   Safari (on macOS 10.13 or later)
>   Chrome (and presumably other Blink-based UAs)
>   MSEdge (on Windows 10 Fall Creators Update or later)
> 
> Bug to turn on by default:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1447163
> 
> This feature was previously discussed in this "intent to implement" thread:
> https://groups.google.com/d/topic/mozilla.dev.platform/_FacI6Aw2BQ/discussion

This sounds great; it's a highly requested feature that's being
shipped with a decent amount of synchronization [1] across multiple
browser engines.

Is there something with a little more detail about how our (a)
feature set and (b) platform support compares with what other
engines are shipping?  That is, are there substantive cases where
some systems will have variation font support on other browsers but
not Firefox, or substantive features that other implementations will
be shipping but we won't?

-David

[1] At least, it's pretty good synchronization compared to the
recent track record in the CSS, fonts, and layout world, though
other parts of the platform have somewhat better records here.

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                          https://www.mozilla.org/   𝄂
             Before I built a wall I'd ask to know
             What I was walling in or walling out,
             And to whom I was like to give offense.
               - Robert Frost, Mending Wall (1914)

Attachment: signature.asc
Description: PGP signature

_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to