[csswg-drafts] [css-fonts-4] Some font features should not be disable-able (#7634)

litherum has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-fonts-4] Some font features should not be disable-able ==
Inside the [Script development specs](https://docs.microsoft.com/en-us/typography/script-development/arabic) section of the OpenType spec, it shows how [certain features](https://docs.microsoft.com/en-us/typography/script-development/arabic#features) are "always applied" for certain scripts.

One reason for this is that these features are required for legibility.

Another reason for this is, in the words of one of our platform text engineers (specifically about Arabic and `rlig`, which is one of the "always applied" features):

> Some Arabic fonts are fantastically complicated with all sorts of interlocking features, and I can imagine at least one of them will break in completely unexpected ways if `rlig` is not applied.

In the Cocoa ports of WebKit, we ensure that these "always applied" features are, in fact, always applied, regardless of what `font-feature-settings` indicates. We believe this is the best policy for user agents in general. We're not aware of any case where an author would intentionally want their text to be broken/illegible, and there are plenty of situations where an author could shoot themselves in the foot by disabling `rlig` (or others) accidentally.

(This is proposal is relevant to [`css/css-fonts/font-variant-ligatures-11.html`](http://wpt.live/css/css-fonts/font-variant-ligatures-11.html), which the Cocoa ports of WebKit are intentionally failing.)

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7634 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 23 August 2022 02:37:31 UTC