On 19/03/2018 22:42, L. David Baron wrote:
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 sounds like it could be a worthwhile blog post somewhere....
In brief: everyone supports font-variation-settings, the most basic tool
authors can use to control these fonts.
The CSS spec also calls for higher-level linkage to (enhanced forms of)
the font-{weight,stretch,style} properties. Edge implements this; Blink
currently accepts [at least some of] the extended CSS values (e.g.
non-integer font-weight values) but doesn't have them hooked up to
variation font rendering; we don't yet implement this.
Regarding platform support: Edge, Safari and Firefox only support
variation fonts on up-to-date versions of Win10 and macOS, while Chrome
(AIUI) also supports them on older versions (by shipping an embedded
copy of FreeType to use in place of the system font rasterizer when it
doesn't have variation support).
On Linux, official Mozilla builds have variation support; distro builds
that use --with-system-freetype will also work provided the system
freetype is fairly recent, but old distros may still have a freetype
that lacks variation support.
I haven't tested recent Chrome on Android but I presume they have the
same support there as on desktop (as does Firefox).
So to sum up....
> That is, are there substantive cases where
> some systems will have variation font support on other browsers but
> not Firefox,
On older releases of macOS and Windows, Chrome will have it but Firefox
won't (neither will Safari/IE/Edge, however).
> or substantive features that other implementations will
> be shipping but we won't?
Support for the enhanced font-{weight,stretch,style} properties is
currently only shipping in Edge, AFAICT; Blink has parsing but not full
rendering support.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
