[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 #8 from Jeff Johnson <opendarwin at lapcatsoftware.com> ---
(In reply to Jonathan Kew from comment #7)
> This bug should be fixed because it breaks interoperability with
> standard-compliant browsers.

Does it break interoperability? As far as I can tell, there doesn't seem to be any actual harm from allowing system-ui to work in local(). In fact, the source of this WebKit bug is a Mozilla bug where the bug reporter expected system-ui to work rather than expecting it to fail:

https://bugzilla.mozilla.org/show_bug.cgi?id=1801687

I would contend that everyone in the world who writes local(system-ui) in CSS expects and hopes for it to work. (Except for someone writing a bug against the spec, for the sole purpose of spec conformance.) To me, allowing system-ui feels like a "victimless crime" against the spec.

This bug isn't requesting a feature to work in Webkit that doesn't currently work; rather, it's requesting a feature to stop working that does currently work in WebKit. A feature that currently benefits some users. I don't see how breaking this feature — especially without any replacement in place — helps browser interoperability or helps WebKit users.


> local() doesn't accept "generic font names" because _they are not "font
> names"_, they represent (potentially composite and/or
> language/locale-dependent) "font family names", which is a different thing.
> 
> As the spec says,
> 
> > The locally-installed <font-face-name> argument to local() is a format-specific string that uniquely identifies a single font face within a larger family.
> 
> That is not what system-ui does.

When I asked "Is there a reason that local() is so restrictive and doesn't accept generic font names?" I wasn't asking for a definition of the spec, I was asking for a practical justification for the spec.

-- 
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/8c7b4e53/attachment.htm>