Conversation
|
🚀 This branch can be previewed at https://6b7d3cef.docs-autonity-org.pages.dev |
|
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?) |
|
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. |
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!?) |
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. |
4 participants
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.