Skip to content

fix font rendering - #281

Merged
aiman merged 1 commit into
masterfrom
fix-font
Dec 3, 2025
Merged

fix font rendering#281
aiman merged 1 commit into
masterfrom
fix-font

Conversation

@flofrie

@flofrie flofrie commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

I noticed that when using Chrome, the body font used throughout the site is extremely thin and very hard to read. This is because the body font-family style defines "proxima nova" as the first entry; on my Ubuntu system, it seems the font of this name is the light version (not regular, which is "Proxima Nova Regular").

Interestingly, this issue does not appear on Firefox (which seems to ignore that entry), and it would not happen on systems where Proxima Nova is not installed.

Having inspected the CSS file, it seems that reference to Proxima Nova is by mistake anyway, since the "Noto Sans" font is included in the CSS, and defined as default for "sans-serif". (Which is indeed what Firefox and systems without Proxima Nova fall back on) -- So, simply removing the "proxima nova" reference entirely returns to expected behaviour.

@github-actions

github-actions Bot commented Nov 6, 2025

Copy link
Copy Markdown

🚀 This branch can be previewed at https://6b7d3cef.docs-autonity-org.pages.dev

@jay-cousins

Copy link
Copy Markdown
Collaborator

Afraid I can't comment on font choices.

(On Chrome on MacBookPro, and on Chrome on Android it looks fine to me atm. I could verify on Linux Ubuntu and Windows 11 if you like?)

@dweng0

dweng0 commented Nov 10, 2025

Copy link
Copy Markdown
Collaborator

Yeah from the looks of it that font family setting was the "default set when the theme file was created and shouldn't be there.
But to the issue of the font itself not working it is a very interesting bug! It appears the font family should be "Proxima Nova" not "proxima nova".

@flofrie

flofrie commented Nov 10, 2025

Copy link
Copy Markdown
Contributor Author

But to the issue of the font itself not working it is a very interesting bug! It appears the font family should be "Proxima Nova" not "proxima nova".

I tried various permutations and none seemed to work, but I didn't explore it further because it shouldn't be there in the first place. (But also: how does one know what font families are available and what their proper names are!?)

@flofrie

flofrie commented Nov 10, 2025

Copy link
Copy Markdown
Contributor Author

Afraid I can't comment on font choices.

No need to comment on font choices. Rather, I'm just requesting approval for removing a reference to a font that does not work in Chrome; renders badly when it does work (in Firefox); and wasn't part of the intended design in the first place.

@flofrie

flofrie commented Dec 3, 2025

Copy link
Copy Markdown
Contributor Author

@aiman , @cmjc , we can't merge this without your approval. This is important, as the Docs site keeps rendering in a barely legible font on some systems.

@jay-cousins jay-cousins left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@aiman
aiman merged commit 2e00b05 into master Dec 3, 2025
3 checks passed
@aiman
aiman deleted the fix-font branch December 3, 2025 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants