-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bug]: h3 to h6 look like text, headings generally inconsistent across apps #43393
Comments
@jancborchardt is this something worth standardizing? |
Yes, sounds good. Could we standardize them all based on the styles from Text? This this is something I went through and balanced back then. |
Sure! That can be copied into the server styles and nextcloud/vue |
Discussed with other engineering leads. The change is simple but the effects are significant and we are close to the feature freeze of 29. We will therefore move this to after the stable29 branch off. |
Sounds reasonable, so merge after branch off? |
Yes :) |
Bug description
h2 isn't great, h3 is bad.
Another example:
Encryption is a h3. It doesn't look like one at all. This makes it super hard to recognize the structure of a text page in Nextcloud, like the settings.
Another one:
Update channel looks like ordinary text. It gives no structure except for the increased spacing.
h1 to h6 all share the same base styling:
server/core/css/styles.scss
Lines 19 to 30 in 375dade
server/core/css/apps.scss
Lines 60 to 78 in 375dade
Steps to reproduce
Expected behavior
Headings that help me recognize the structure of text, paragraphs and sections.
Installation method
None
Nextcloud Server version
master
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: