W3C home > Mailing lists > Public > www-style@w3.org > March 2012

Re: [css3-fonts] simplifying font-variant-ligatures, proposal 2

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Mon, 26 Mar 2012 16:58:53 +0200
Message-Id: <E7A940F4-BDA9-4F9E-B856-058DFD4BA5B6@crissov.de>
To: "www-style@w3.org Style" <www-style@w3.org>
Eric Muller:
> On 2/22/2012 9:22 PM, John Daggett wrote:
>>  font-variant-ligatures: normal | inherit | no-ligatures | [ common-ligatures || discretionary-ligatures || historical-ligatures ]
> [...]
>> The only situation this wouldn't cover would be one where an author explicitly wants to disable common ligatures but wants to enable only historical ligatures (…).
> 
> More generally, I don't see how to write a rule that disables something (…) without knowing what's enabled in the parent context.

Do you have a usecase, though? The WG shoots down ideas on a regular basis that are technically possible but unlikely to be used.

We could still introduce subsubproperties in a later level nevertheless:

                                     fo(n|rma)t    true     false    parent
  font-variant-ligatures-common:        _auto_ |  normal  |  none  | inherit
  font-variant-ligatures-contextual:    _auto_ |  normal  |  none  | inherit
  font-variant-ligatures-discretionary:  auto  |  normal  | _none_ | inherit
  font-variant-ligatures-historical:     auto  |  normal  | _none_ | inherit
  font-variant-ligatures-required:       auto  | _normal_ |  none  | inherit

(Underscores mark initial value.)
Received on Monday, 26 March 2012 14:59:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:48:53 GMT