-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Commit and PR diff view does not honour spaces/tabs #13406
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
Comments
Broken here: 4617bb6#diff-5d1373f9290f762a4751c497b0e8be279eb04caa3a7cdc2fd3f42b9f505a83beL188-R192 Since we loose mono.wrap > whitespace: pre |
Argh, LESS strikes again, I didn't notice those additional child selectors when moving the |
It's worth noting that your changes to the mono class will have improved the appearance of the extended commit messages |
as I suggested on #maintainers I think if we change box.tmpl et al to use |
Yeah, |
- Introduce new .code-inner class that sets the CSS attributes on rendered code lines like view,blame and diff. - Rename .wrap class to .word-break to reflect what it actually does - Remove .raw which was only used on webhook page - Set white-space: pre-wrap except on blame where it can break the layout Fixes: go-gitea#13406
- Introduce new .code-inner class that sets the CSS attributes on rendered code lines like view,blame and diff. - Rename .wrap class to .word-break to reflect what it actually does - Remove .raw which was only used on webhook page - Set white-space: pre-wrap except on blame where it can break the layout Fixes: #13406
[x]
):Description
Diff view on a commit as well as PRs does not honour spaces or tabs anymore.
The file view itself still does tho.
Recreated here:
The file with spaces and tabs: https://try.gitea.io/lynxplay/testing-gittea/src/branch/master/file-with-spaces.txt
The diff commit view without them: https://try.gitea.io/lynxplay/testing-gittea/commit/4c8fd6c646fe172d0d00d613dd9babfa3cebc965
PR files view: https://try.gitea.io/lynxplay/testing-gittea/pulls/3/files
Screenshots
The text was updated successfully, but these errors were encountered: