Skip to content
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

Flags Page Defaults to Serif Font #7208

Closed
kuesa opened this issue Dec 4, 2019 · 3 comments
Closed

Flags Page Defaults to Serif Font #7208

kuesa opened this issue Dec 4, 2019 · 3 comments
Labels
Chromium/waiting upstream Issue is in Chromium; we'll likely wait for the fix priority/P5 Not scheduled. Don't anticipate work on this any time soon.

Comments

@kuesa
Copy link

kuesa commented Dec 4, 2019

Description

The flags page (brave://flags) defaults to a serif font. This is because in Chromium, the Roboto font is provided as a resource, but it is not included in the Brave browser (at least on the flags page). Since the styling for the flags page only specifies Roboto as the font family, and the body style overrides the default text CSS, and since Roboto is not provided, the font defaults to being the default serif font.

Steps to Reproduce

  1. Open Brave Browser on Desktop
  2. Navigate to brave://flags

Actual result:

The body fonts are in a serif font family.

Expected result:

The body fonts to be in a sans-serif font family, to be consistent with the rest of the UI:

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

Brave | 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-bit)
Revision | 4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889}
OS | Windows 10 OS Version 1903 (Build 18362.476)

Version/Channel Information:

  • Can you reproduce this issue with the current release? You Betcha
  • Can you reproduce this issue with the beta channel? Yes
  • Can you reproduce this issue with the dev channel? Yes
  • Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? No
  • Does the issue resolve itself when disabling Brave Rewards? No
  • Is the issue reproducible on the latest version of Chrome? No (since Chrome provides Roboto)

Miscellaneous Information:

This might be an issue to bring up with the Chromium repo, since it might be bad practice to only specify one font, and not alternatives.

@kuesa kuesa changed the title Flags Page defaults to Serif Font Flags Page Defaults to Serif Font Dec 4, 2019
@kuesa
Copy link
Author

kuesa commented Dec 4, 2019

Submitted a PR to fix this issue in the Chromium repo: #33

@rebron rebron added Chromium/waiting upstream Issue is in Chromium; we'll likely wait for the fix priority/P5 Not scheduled. Don't anticipate work on this any time soon. labels Jan 31, 2020
@rebron
Copy link
Collaborator

rebron commented Jan 31, 2020

@kuesa Thanks for taking this one on. We'll wait for this fix to come through via upstream.

@bsclifton
Copy link
Member

Closing as there is no action we can take here. @kuesa I've never submitted a patch through Chromium GitHub repo- I've only seen work accepted when going through https://chromium-review.googlesource.com/

Let me know if you need help getting started contributing upstream; There's a great guide here which goes over creating a CL, etc
https://chromium.googlesource.com/chromium/src/+/master/docs/contributing.md

@bbondy bbondy added this to the Closed / Invalid milestone Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chromium/waiting upstream Issue is in Chromium; we'll likely wait for the fix priority/P5 Not scheduled. Don't anticipate work on this any time soon.
Projects
None yet
Development

No branches or pull requests

4 participants