-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@font-face/src incorrectly describes the values accepted by the local()
specifier
#12347
Comments
Hi @nk9, I just checked the section referenced by you and it seems that perhaps the content has already been corrected.
It currently states:
Hope that's clear about what arguments are accepted by |
Closing per #12347 (comment) |
Side note that these pages have been refreshed recently in: |
Thanks for this, glad to see the docs have been corrected. However, I notice that the new wording still doesn't explicitly include the W3C recommendation about using both names:
The first Example block does contain a |
Thanks @nk9 for following up on this. I have raised a PR to add the recommendation.
I do see that examples on the W3C page also omit providing both names at times, I suppose that's fine if some examples are not focused particularly on the |
What page(s) did you find the problem on?
Specific page section or heading?
@font-face/src
, Formal SyntaxWhat is the problem?
The Formal Syntax claims that the value which should be passed to
local()
is the "family-name". In fact, the CSS spec makes clear that the value should describe the font face:This piece of advice seems super relevant for web developers.
Did you test this? If so, how?
I discovered this issue while testing with Firefox, Chrome and Safari on macOS 11.6.2. Firefox and Chrome generally require e.g.
local("Helvetica-Oblique")
here to render an italic version of the font, whereas Safari happily acceptslocal("Helvetica")
and works out which font face is meant. You can use the following code on different browsers to see the issue:The text was updated successfully, but these errors were encountered: