-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Introduce --page-space-bottom
at 64px
#30692
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
Conversation
--page-spacing
Why not 80px? I'm suitable to have more space. Too little space makes me feel stressful. |
Likely should use a new variable like |
The project view has been improved by " Add fullscreen mode as a more efficient operation way to view projects #34081 " . Even in non-fullscreen mode, the column heights are all correctly set by So the "bottom padding" could be kept as old, I also agree that the old design looks more comfortable. |
--page-spacing
--page-margin-bottom
at 64px
Looking good now? The variable name can be bikeshed over, it's actually setting |
Maybe |
--page-margin-bottom
at 64px--page-space-bottom
at 64px
Renamed. |
* giteaofficial/main: Fix button alignments (go-gitea#34276) Update token creation API swagger documentation (go-gitea#34288) [skip ci] Updated translations via Crowdin Explicitly not update indexes when sync database schemas (go-gitea#34281) Introduce `--page-space-bottom` at 64px (go-gitea#30692) # Conflicts: # templates/repo/wiki/revision.tmpl
Previously we would always leave 80px space before the page footer, but this is problematic with small viewport heights on projects page for example. I think it' ideal that we use
--page-spacing
which is already in use for spacing on top of the page.The
secondary-nav
margin is also adjusted as I see no value why this shouldn't be the same value.