-
-
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
Login UI layout issue, the top marin of the login div missed. #29981
Comments
Regression of #29922? @silverwind The margin of page-content was removed:
|
What exactly is necessary to reproduce the tabbar-less login ui? |
I think We should use margin for outer spaces as much as possible. They could overlap gracefully. |
No, I think the content should itself decide whether it wants margin or not. Many tabbars want 0 margin. It's not for the |
And @lunny don't call it broken. A minor layout issue is far from "broken" :) |
The problem is the negative margins from fomantic on |
Please help me to change it to a proper word. |
I would call it "misaligned", or "incorrect render". |
…ally (#29982) Fixes: #29981. Introduce `.secondary-nav` as a universal way for styling and margin adjustments inside `.page-content`. If the first child of `.page-content` is `.secondary-nav`, we add margin below it, otherwise we add padding to the first child. Notable changes: - `--color-header-wrapper` is replaced with `--color-secondary-nav-bg`. - `navbar` class is removed. --------- Co-authored-by: Giteabot <teabot@gitea.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
…nt` spacing universally Fixes: go-gitea/gitea#29981. Introduce `.secondary-nav` as a universal way for styling and margin adjustments inside `.page-content`. If the first child of `.page-content` is `.secondary-nav`, we add margin below it, otherwise we add padding to the first child. Notable changes: - `--color-header-wrapper` is replaced with `--color-secondary-nav-bg`. - `navbar` class is removed. Co-authored-by: Giteabot <teabot@gitea.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> --- Conflict resolution: Trivial conflict & changed selector to reflect new classes. Ref: https://codeberg.org/forgejo/forgejo/issues/2776 (cherry picked from commit 3ccda41a539b8ba7841919ee12dc2877ddc03818)
The text was updated successfully, but these errors were encountered: