W3C home > Mailing lists > Public > www-style@w3.org > August 2015

Re: [css3-fonts] "inherit" value of font-feature-settings

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 12 Aug 2015 09:34:11 -0700
Message-ID: <CAAWBYDDcx19=oZOjrOA3qZKuRAub_0WDG3dC5yV6kQezmce8kw@mail.gmail.com>
To: "Myles C. Maxfield" <mmaxfield@apple.com>
Cc: www-style list <www-style@w3.org>
On Tue, Aug 11, 2015 at 7:08 PM, Myles C. Maxfield <mmaxfield@apple.com> wrote:
> The CSS3 fonts spec defines the font-feature-settings property to be inherited. Because of this, it's easy for an inner element which wants to use some font feature to clobber some other font feature specified on an ancestor, which is probably not what authors want or intend. It would be better if font-feature-settings performed a union between the elements specified style and its inherited style. Removing the use of font features can be accomplished with the "normal" keyword. Please note that there is precedence for this behavior; please see the text-decoration property.

text-decoration uses a separate, "magical" inheritance of the
decorations themselves.  It's a one-off and pretty complicated, and we
don't want to duplicate its mechanics elsewhere.

As John says, using the individual font-variant properties reduces the
chances of collisions.  Use of font-feature-settings is discouraged;
it's only really there to allow activating arbitrary features that
fonts might have which aren't captured by CSS.

That said, it's still possible to have collisions!  This is a generic
problem in CSS; every list-valued property has this.  We need to solve
this at some point, in some way. :/

~TJ
Received on Wednesday, 12 August 2015 16:34:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 August 2015 16:34:58 UTC