-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Incorrect font size for PR/issue comment #17480
Comments
Gusted
pushed a commit
to Gusted/gitea
that referenced
this issue
Nov 7, 2021
- Fixes a issue that started from go-gitea#17317 - Move `> .merge-section` to the `> .content` scope. - Resolves go-gitea#17480
Hi @proton-ab! Thanks for reporting the issue, it will be fixed by #17582. |
Chianina
pushed a commit
to Chianina/gitea
that referenced
this issue
Mar 28, 2022
* Move `> .merge-section` to `> .content` scope - Fixes a issue that started from go-gitea#17317 - Move `> .merge-section` to the `> .content` scope. - Resolves go-gitea#17480 * Move `.merge-section` back to outside scope Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gitea Version
f46e67b
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker image
gitea/gitea:dev-rootless
Database
No response
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
Font size for PR/issue comment is incorrect. It is using 16px inherited from
.markdown
class when it should be using its own overridden 14px. The issue occurred between 58cd55d (known good) and 2b2eb5d (known bad) but since half the commits have broken CI run I can't really test them properly without setting up full development environment.See this try page for example: https://try.gitea.io/ChristopherHX/actions-on-gitea/pulls/2
On v1.15.6 this is handled by (generated code):
On broken version we can see this instead:
Screenshots
Bad (current):
Good (simulated):
The text was updated successfully, but these errors were encountered: