-
Notifications
You must be signed in to change notification settings - Fork 309
ui: Use "Source Sans 3" font for most UI text #294
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
Labels
a-design
Visual and UX design
Milestone
Comments
gnprice
pushed a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Sep 1, 2023
It's strange that iOS really doesn't seem to know what to do with 'sans-serif' here. Nor "SF Pro", "SF-Pro", nor any obvious variation on that, even though it's supposedly the system font: https://developer.apple.com/fonts/ But a GitHub comment popped up a few hours ago (linked in the added code), and that's the first thing I've found that seems to work, as a clear pointer to the default system font. Shrug. Later, we'll want to use Source Sans 3 for almost all the text in the app. But we'll want to take more care with that than I have bandwidth for right now (around it being a variable-weight font); see zulip#294. Fixes: zulip#289
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Nov 15, 2023
From looking at the "Computed" tab in the Chrome DevTools element inspector, on CZO at 8.0-dev-2850-gef1c1ce05f. Technically the web app has a computed `line-height` of 16.996px, but that seems like a rounding error. One reason for doing this now is to opt out of a default that would take effect with the upcoming migration to Material 3. The text would otherwise get a line height of 1.43 times the font size, and we want it to be denser than that. We briefly explored how to preserve the line height exactly, across the M3 migration, but the solutions we found seemed more awkward than just taking care of this: zulip#380 (comment) Fixes-partly: zulip#294
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Nov 15, 2023
Values obtained by looking at the "Computed" tab in the Chrome DevTools element inspector, on CZO at 8.0-dev-2850-gef1c1ce05f. Technically the web app has a computed `line-height` of 16.996px, but that seems like a rounding error. One reason for doing this now is to opt out of a default that would take effect with the upcoming migration to Material 3. The text would otherwise get a line height of 1.43 times the font size, and we want it to be denser than that. We briefly explored how to preserve the line height exactly, across the M3 migration, but the solutions we found seemed more awkward than just taking care of this now: zulip#380 (comment) Fixes-partly: zulip#157 Fixes-partly: zulip#294
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Nov 16, 2023
Values obtained by looking at the "Computed" tab in the Chrome DevTools element inspector, on CZO at 8.0-dev-2850-gef1c1ce05f. Technically the web app has a computed `line-height` of 16.996px, but that seems like a rounding error. One reason for doing this now is to opt out of a default that would take effect with the upcoming migration to Material 3. The text would otherwise get a line height of 1.43 times the font size, and we want it to be denser than that. We briefly explored how to preserve the line height exactly, across the M3 migration, but the solutions we found seemed more awkward than just taking care of this now: zulip#380 (comment) Fixes-partly: zulip#157 Fixes-partly: zulip#294
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Dec 6, 2023
…styles With plumbing to make kDefaultFamily work, since it's a variable-weight font. As it happens, most -- perhaps all -- of the app's text is built on Typography styles. See the next commit for some thoughts on that. Since that's the case, I'll mark this commit as fixing these issues: - zulip#294 "Use "Source Sans 3" font for most UI text" - zulip#438 "Consistently use "Noto Color Emoji" for emojis on Android". If there's some corner of the app where the two fonts aren't getting applied, we'll eventually find it, and apply kDefaultFontFamily and kDefaultFontFamilyFallback according to their doc comments, to fix. Fixes: zulip#294 Fixes: zulip#438
gnprice
pushed a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Jan 5, 2024
…styles With plumbing to make kDefaultFamily work, since it's a variable-weight font. As it happens, most -- perhaps all -- of the app's text is built on Typography styles. See the next commit for some thoughts on that. Since that's the case, I'll mark this commit as fixing these issues: - zulip#294 "Use "Source Sans 3" font for most UI text" - zulip#438 "Consistently use "Noto Color Emoji" for emojis on Android". If there's some corner of the app where the two fonts aren't getting applied, we'll eventually find it, and apply kDefaultFontFamily and kDefaultFontFamilyFallback according to their doc comments, to fix. Fixes: zulip#294 Fixes: zulip#438
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Jan 5, 2024
With plumbing to make kDefaultFamily work, since it's a variable-weight font. As it happens, most -- perhaps all -- of the app's text is built on Typography styles. See the next commit for some thoughts on that. Since that's the case, I'll mark this commit as fixing these issues: - zulip#294 Use "Source Sans 3" font for most UI text - zulip#438 Consistently use "Noto Color Emoji" for emojis on Android If there's some corner of the app where the two fonts aren't getting applied, we'll eventually find it, and apply kDefaultFontFamily and kDefaultFontFamilyFallback according to their doc comments, to fix. Fixes: zulip#294 Fixes: zulip#438
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Jan 9, 2024
With plumbing to make kDefaultFamily work, since it's a variable-weight font. As it happens, most -- perhaps all -- of the app's text is built on Typography styles. See the next commit for some thoughts on that. Since that's the case, I'll mark this commit as fixing these issues: - zulip#294 Use "Source Sans 3" font for most UI text - zulip#438 Consistently use "Noto Color Emoji" for emojis on Android If there's some corner of the app where the two fonts aren't getting applied, we'll eventually find it, and apply kDefaultFontFamily and kDefaultFontFamilyFallback according to their doc comments, to fix. Fixes: zulip#294 Fixes: zulip#438
chrisbobbe
added a commit
to chrisbobbe/zulip-flutter
that referenced
this issue
Feb 2, 2024
With plumbing to make kDefaultFamily work, since it's a variable-weight font. As it happens, most -- perhaps all -- of the app's text is built on Typography styles. See the next commit for some thoughts on that. Since that's the case, I'll mark this commit as fixing these issues: - zulip#294 Use "Source Sans 3" font for most UI text - zulip#438 Consistently use "Noto Color Emoji" for emojis on Android If there's some corner of the app where the two fonts aren't getting applied, we'll eventually find it, and apply defaultFontFamily and defaultFontFamilyFallback according to their doc comments, to fix. Fixes: zulip#294 Fixes: zulip#438
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since Source Sans 3 is a variable-weight font, we'll have to take some extra care not to regress on support for the user's "use bold text" accessibility setting. We've been doing that by styling text with a
TextStyle
object that comes fromweightVariableTextStyle
(or is merged with one that comes from that). Pass aBuildContext
to that function to let it conditionalize on that accessibility setting.One might normally set a "default font" for the app without using
TextStyle
objects: by settingfontFamily
orfontFamilyFallback
on an app-wideThemeData
. ButThemeData
doesn't also have afontVariations
field, which controls text weight for weight-variable fonts.Discussion: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/flutter.3A.20text.20all.20weird/near/1633648
The text was updated successfully, but these errors were encountered: