W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2016

[csswg-drafts] [css-fonts] Feature resolution and caps synthesis conflicting

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Jul 2016 18:19:53 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-163448750-1467397191-sysbot+gh@w3.org>
tabatkins has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-fonts] Feature resolution and caps synthesis conflicting ==
**On Fri, Jul 1, 2016 at 2:08 AM, Dominik Röttsches <drott@google.com>
 wrote:**
> Hi,
>
> consider the following example:
>
> span {
> font-variant-caps: all-small-caps;
> font-feature-settings: "smcp" 0, "c2sc" 0;
> }
>
> https://drafts.csswg.org/css-fonts/#feature-precedence says that at
> font-variant-caps should be take into account at precedence level 4,
> however, at level 6 it is overriden by font-feature-settings. 
>
> The synthesis rules in
> https://drafts.csswg.org/css-fonts/#propdef-font-variant-caps 
describe that
> if none of the native features are available, all-small-caps should 
be
> synthesized by upper-casing the text and downscaling the font.
>
> However, what should be the exact definition of availability here, 
taking
> into account the feature resolution?
>
> The feature resolution can be interpreted in two ways:
> 1) It means it should deactivate/hide the available features in the 
font and
> trigger synthesis since the resolved available feature set does not 
have
> smcp and c2sc, or alternatively, 
> 2) no synthesis is done since the feature detection has determined 
that the
> features are available and should be enabled through 
font-variant-caps, but
> then are deactivated through font-feature-settings.
>
> Opinions? What should happen in this case -

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/259 using your GitHub 
account
Received on Friday, 1 July 2016 18:20:02 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:00 UTC