-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Most recent commit with long first line causes repo view to overflow #22360
Comments
I was able to fix it on my end without effecting the other page with a header template file containing:
|
Fix suggestion in #22413 (comment). |
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Jan 20, 2023
There was an unintended regression in go-gitea#21124 which assumed that `.commits-list .message-wrapper` would only match the commit summaries on `/{owner}/{name}/commits/*`. This assumption is incorrect as the directory/file view also uses a `.commits-list` wrapper. Rather than completely restructure this page this PR simply adjusts the styling to again use `display: inline-block;` for `#repo-files-table .commit-list .message-wrapper` Fix go-gitea#22360 Signed-off-by: Andrew Thornton <[email protected]>
yardenshoham
added a commit
to yardenshoham/gitea
that referenced
this issue
Jan 20, 2023
Backport go-gitea#22551 There was an unintended regression in go-gitea#21124 which assumed that .commits-list .message-wrapper would only match the commit summaries on /{owner}/{name}/commits/*. This assumption is incorrect as the directory/file view also uses a .commits-list wrapper. Rather than completely restructure this page this PR simply adjusts the styling to again use display: inline-block; for #repo-files-table .commit-list .message-wrapper Fix go-gitea#22360
lunny
pushed a commit
that referenced
this issue
Jan 20, 2023
There was an unintended regression in #21124 which assumed that `.commits-list .message-wrapper` would only match the commit summaries on `/{owner}/{name}/commits/*`. This assumption is incorrect as the directory/file view also uses a `.commits-list` wrapper. Rather than completely restructure this page this PR simply adjusts the styling to again use `display: inline-block;` for `#repo-files-table .commit-list .message-wrapper` Fix #22360 Signed-off-by: Andrew Thornton <[email protected]>
lunny
pushed a commit
that referenced
this issue
Jan 20, 2023
Backport #22551 There was an unintended regression in #21124 which assumed that .commits-list .message-wrapper would only match the commit summaries on /{owner}/{name}/commits/*. This assumption is incorrect as the directory/file view also uses a .commits-list wrapper. Rather than completely restructure this page this PR simply adjusts the styling to again use display: inline-block; for #repo-files-table .commit-list .message-wrapper Fix #22360
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Hello.
The changes in #21124, specifically here cause the repo file browser to overflow off the page when the most recent commit message has a long first line, which happens a lot when using the Gitea UI to merge two branches with median-length first lines, by default.
By having
display: inline
, the.commit-list .message-wrapper
in the repository file browser doesn't respect themax-width
to prevent overflow.Changing
display: inline
todisplay: inline-block
fixes the issue on the repository page, but breaks the changes in the above PR, otherwise I would have submitted a PR for it.I cannot reproduce on the Gitea demo site because it won't allow me to create an account (500 error).
Screenshots
(Sorry for the obfuscation, I couldn't create an account on the demo site, otherwise I would have used that.)
Gitea Version
1.18.0
Can you reproduce the bug on the Gitea demo site?
No
Operating System
Linux
Browser Version
Firefox 108.0, Google Chrome 108.0.5359.124
The text was updated successfully, but these errors were encountered: