-
Notifications
You must be signed in to change notification settings - Fork 17
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
Mention system-ui
and ui-*
#25
Comments
Not mentioning system-ui might not be about browser support, but rather about i18n: https://infinnie.github.io/blog/2017/systemui.html Back in 2017 this was apparently a whole thing with Bootstrap opting out of system-ui (twbs/bootstrap#22377). They added it again in 2020 (twbs/bootstrap#30561) though someone still had issues after the release (twbs/bootstrap#30561 (comment)). Looking at recent related discussions at Gitea (go-gitea/gitea#14575) and iFixit (iFixit/core-primitives#36), it seems that system-ui (before Segoe) is still not a good idea. Best would be to test on a VM with Windows in Chinese, though |
The 2017 article does not mention one thing: On several Windows browsers, Plus |
@Artoria2e5 thank you! So you're saying that after Windows 7, If that's accurate, then |
That’s correct. The source for what system-ui resolves to is simply the linked article; the screenshot for Windows 8.1 is enough evidence. It’s really more about how you look at it: sure it doesn’t have the font weights you want, but it’s better than the alternative of a more broken Windows 7 (Vista too, I recall!) did use YaHei in most of the actual system UI, but it’s possible that the whatever API that gives out the system-ui value wasn’t changed. Microsoft Yahei UI (yes, it’s different, like Segoe vs Segoe UI) was introduced in 8 iirc. 1 That said, So the situation is:
|
At least
system-ui
seems widespread enough for usage.The text was updated successfully, but these errors were encountered: