Re: [css3-fonts] default font features

I must say that I'd expect that font-feature-settings: normal does not neces=
sarily produce considtent results across browsers. To me, it's something lik=
e 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 s=
ome other features by default. I can sympathize with that. After all, they d=
o have their text-rendering: optimizeLegibility property. I would, however, e=
xpect 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: d=
efault -- this would work differently from normal. The value normal should l=
eave all the decisions to the browser whether to apply any features at all. T=
he value default would apply all the default features, which should perhaps b=
e enumerated by the spec.=20

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

Best,
Adam

Sent from my mobile phone.

On 07.07.2012, at 07:16, John Daggett <[email protected]> wrote:

> Adam Twardoch wrote:
>=20
>> 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?
>=20
> 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).=20
>=20
> Cheers,
>=20
> John