-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Bold text no longer displayed as bold #24835
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
Comments
I am 99.99% sure it's related to your browser & font system .... Does #24305 help? (a test link https://codepen.io/silverwind/pen/jOeBmvj ) , ps: there is also a following PR #24827 to reset the bold value to 600 from 601. |
Yeah the test link gives inconsistent results. 700 is proper bold. IIRC that is also the weight I'd always had to use when menually setting these values in my web design way back when. having it at 600 would work on my system, obviously (Windows 10 22H2, Radeon graphics). The linked issue doesn't really give a solution how to solve this in my installation though. I'd be happy to just set it to 600 or |
The context is here : #24305 (comment) |
Here it is. |
Thanks, but... how do I apply that to my system? I'm a binary user -- I tend to use it stock (since I had nightmares previously using custom templates) |
Thanks, I appreciate the help! |
FTR I went the custom template route (not comfortable running a nightly on a pivotal production repo): <style>
:root {
--font-weight-bold: 600;
}
</style> Which fixes the issue on my setup. I'm thinking this may be a quirk of the Segoe font specifically? Either way, since it's already addressed in the PR otherwise I'll just close this. |
Description
With one of the recent updates of our self-hosted Gitea (probably when moving to 1.19.3 from 1.18.*) some formatting no longer applies.
Most notably, headers and bold text is no longer rendered as such.
I checked the CSS involced and found:
It seems the
--font-weight-bold
value is not filled properly or set to a bad value.This occurs in the Pale Moon web browser. It does not occur in Edge.
Gitea Version
1.19.3
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
https://repo.palemoon.org/MoonchildProductions/UXP/issues/2252#issuecomment-36448

Git Version
2.39.2, Wire Protocol Version 2 Enabled
Operating System
CentOS
How are you running Gitea?
x86_64 Linux binary downloaded from gitea.io
Database
MySQL
The text was updated successfully, but these errors were encountered: