Hi,

I noticed the "motivation" was removed from the email draft generated by chromestatus. So let's put it here:

"The "-webkit-standard" name is used internally to describe a default font family that can be configured via a user preference. It's implicitly used internally (e.g. for initial or fallback font) or explicitly by authors via the proprietary name "-webkit-body". However because of how this is implemented, authors can also just specify "-webkit-standard" and obtain similar web-exposed behavior. Removing special behavior for these proprietary value will improve alignment with the CSS specifications and Firefox."

Just to make sure we are all on the same page, this intent is to remove this special behavior for explicit "-webkit-standard" families. The internal use for default/fallback fonts as well as support for "-webkit-body" are out of the scope of this intent.


Le 16/11/2021 à 15:46, Frédéric Wang a écrit :


        Contact emails

fw...@igalia.com <mailto:fw...@igalia.com>, ssin...@igalia.com <mailto:ssin...@igalia.com>


        Explainer

None


        Specification

https://drafts.csswg.org/css-fonts-4/#font-family-prop <https://drafts.csswg.org/css-fonts-4/#font-family-prop>


        Summary

Remove support for the font-family value "-webkit-standard". This essentially behaves as an alias to the proprietary keyword "-webkit-body" and is only exposed as historical implementation details inherited from WebKit.


        Blink component

Blink>Fonts <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink>Fonts>


        TAG review


        TAG review status

Not applicable


        Risks



        Interoperability and Compatibility

This will make Blink more aligned with the spec and with Firefox, but no longer aligned with WebKit. Although not recommended, people can continue to use the proprietary name "-webkit-body" to preserve existing behavior. In March 2020, searching these strings on HTTPArchive gave 2738 matches over ~5 millions (~0.05%). For better accuracy, a use counter was added which is located at the place where this generic name is actually tested and resolved to a more precise name. This counter also excludes other internal uses of that string, as mentioned above. On November 1st, reported measurement was ten times smaller that HTTPArchive (~0.005%): https://chromestatus.com/metrics/feature/timeline/popularity/3987 <https://chromestatus.com/metrics/feature/timeline/popularity/3987>



/Gecko/: Shipped/Shipping Firefox does not support this -webkit prefixed value.

/WebKit/: Neutral (https://github.com/web-platform-tests/wpt/pull/22512#discussion_r399764967 <https://github.com/web-platform-tests/wpt/pull/22512#discussion_r399764967>) As a general rule, Apple is against removing features if that can break things on the web or their platform. Myles C. Maxfield commented that he is aware of the issue and don't think it's something desirable that these values are web-exposed.

/Web developers/: No signals It's not clear whether developers are actually aware of this behavior but it was used by a few pages (see compat analysis).

/Other signals/:


        Debuggability

font-family is exposed via usual CSS DevTools.



        Is this feature fully tested by web-platform-tests
        
<https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>?

Yes


        Flag name



        Requires code in //chrome?

False


        Estimated milestones

No milestones specified



        Link to entry on the Chrome Platform Status

https://www.chromestatus.com/feature/5639265565278208 <https://www.chromestatus.com/feature/5639265565278208>

This intent message was generated by Chrome Platform Status <https://www.chromestatus.com>.


PS: For those interested in that one and other font-family stuff, there will be a breakout session on day 2 of BlinkOn 15.


--
Frédéric Wang
--
You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org <mailto:blink-dev+unsubscr...@chromium.org>. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/958f3a2d-c47a-7b37-7a05-46e4d8ace894%40igalia.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/958f3a2d-c47a-7b37-7a05-46e4d8ace894%40igalia.com?utm_medium=email&utm_source=footer>.


--
Frédéric Wang

--
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5d81662a-f852-4267-0e6f-868bcd167de7%40igalia.com.

Reply via email to