Re: [css3-fonts] computed style for font-feature-settings?

On Fri, May 31, 2013 at 2:24 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> On Fri, May 31, 2013 at 12:55 PM, Glenn Adams <glenn@skynav.com> wrote:
> > Earlier I referred to the potential need for an OM API to enumerate the
> > features supported by a platform or a font. There is a somewhat related
> > question, which is: what features should be enumerated when obtaining the
> > computed value for font-feature-settings? Should every feature of the
> font
> > be returned with the current value? Should, in addition, features
> supported
> > by the platform but not the font be included? Should the return value
> also
> > take into account side-effects on features from other properties, such as
> > font-kerning: none or font-variant-ligatures: none [which can have such
> > effects as causing 'kern' 0, 'liga' 0, etc.)?
>
> The computed value is "as specified".  You get out the same values you put
> in.
>

Ah, thanks, I'd missed the Computed value line. I guess it was too much to
hope that it would be possible to indirectly discover the font's supported
features through getComputedStyle.