[Webkit-unassigned] [Bug 248656] `system-ui` should not be treated as a font face name in `src:local(...)`

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=248656

--- Comment #10 from Jeff Johnson <opendarwin at lapcatsoftware.com> ---
(In reply to Jonathan Kew from comment #9)
> If the webkit bug here is fixed so as to conform to the specification, any
> Safari-using authors who want their page to use the macOS system font will
> be nudged to use the system-ui keyword in the manner the spec intends (as a
> value in the font-family list) and it'll work consistently across all the
> browsers.

This misses an important use case, which I mentioned earlier: "I know a lot of Apple users use a custom style, either in a user style sheet or a browser extension, to replace page fonts with the default system font." It's not just about page authors.

It's not just a Safari/Apple issue either. In general, CSS writers are confused about why @font-face behaves differently and has different rules than the CSS font property. We use generics in font-family so why not @font-face? Is there a good reason why we can't use local(sans-serif) for example? I don't see why it ought to be restricted from using generics, regardless of browser or platform. system-ui is a prominent example, because Apple has a vendor-specific system font, but the question of why local() can't use generics is broader. I suspect that more CSS authors would use it if it were possible.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221222/602b748e/attachment-0001.htm>