Re: [css3-fonts] default font features

I must say that I'd expect that font-feature-settings: normal does not necessarily produce considtent results across browsers. To me, it's something like font-family: serif -- it's up to the browser how to interpret it precisely.

It is known that WebKit tries to render text fast by disabling kerning and some other features by default. I can sympathize with that. After all, they do have their text-rendering: optimizeLegibility property. I would, however, expect that with that setting, WebKit should apply all the default features (for standard scripts: ccmp, locl, mark, mkmk, liga, kern, perhaps also rlig, clig and calt). If it does not, I'd consider this a bug.

Alternatively, I'd recommend an additional value for font-feature-settings: default -- this would work differently from normal. The value normal should leave all the decisions to the browser whether to apply any features at all. The value default would apply all the default features, which should perhaps be enumerated by the spec. 

So the value default would be more restrictive: it would say "do apply features, whatever they might be". The value normal would just say "it's up to you whether to apply any features or none at all". 

Best,
Adam

Sent from my mobile phone.

On 07.07.2012, at 07:16, John Daggett <jdaggett@mozilla.com> wrote:

> Adam Twardoch wrote:
> 
>> I think this comparison would be even more useful if you add #p3
>> which does not specify any font-feature-settings at all (i.e. not
>> even "normal"). Is the behavior the same as with "normal" for each
>> browser?
> 
> Since 'normal' is the default value, that's equivalent to not including
> it at all (assuming the property is not used in a default user agent
> stylesheet which this property is not). 
> 
> Cheers,
> 
> John

Received on Saturday, 7 July 2012 09:51:12 UTC