-
Notifications
You must be signed in to change notification settings - Fork 642
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
[css-fonts] Should font-synthesis be reset by font shorthand? #1032
Comments
Why should it be reset when none of its values are present in the shorthand? That doesn't make any sense. Just because it starts with the word |
Many other font properties do not have any value present in the shorthand, but they are still reset, which makes sense because author should expect But, yeah, whether If it is intentional that
WDYT? |
I don't have a strong preference. I'm happy to put it in. |
There's a similar note wrt |
I agree that this shouldn't be reset by 'font'; whether you want to synthesize bolds/etc is mostly independent of the font you choose. |
@upsuper do you agree with tab that this should not reset? |
I don't have strong opinion either way. Given @tabatkins and @litherum prefer that way, I'm fine with that. I still think it's worth a note in the spec, though. |
Happy to note in the spec that this is not reset by the font shorthand. |
On the other hand, we already had (my italics):
Edited to add: that language was in an older version of the draft, but not in the current version. The new version has different language to express the same thing. So it certainly seems worthwhile to explicitly state that |
The spec doesn't mention
font-synthesis
as a subproperty offont
shorthand, but given its name, it probably should be.Gecko resets
font-synthesis
when settingfont
, while WebKit doesn't.Test code:
cc @nattokirai @litherum
The text was updated successfully, but these errors were encountered: