-
-
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
README WordPress the code is overflowing #6679
Comments
Did you try: pre {
white-space: pre-wrap;
} |
Nice ! Thank you ! Change the CSS is better. Can you add this fixe ? Where i can add this code ? |
You could add this somewhere in However, keep in mind HTML rendering was shut off on purpose, to prevent XSS attacks. |
Ok I will make a proposal to update this file, with your CSS fix thank you very much. https://github.com/go-gitea/gitea/blob/master/public/less/_repository.less |
Some checks haven’t completed yet Merging is blocked |
kolaente say : That's changing the code-diff view, not the readme. Ok, that's not what's wanted then. An idea of CSS to modify? |
Return of the administrator who deployed our GITEA. I installed gitea via the docker I can not find the CSS files in it; I understand half that slab to docker, I think I have a docker-dial that assembles a docker gitea that is elsewhere with its own files |
semantic.min.css is not the place to add the changes, as that is a separate project (https://github.com/Semantic-Org/Semantic-UI). Adding it to _repository.less is fine. You just added it at the wrong line (see my comment in your PR). ;) |
saitho say : Rebuild the CSS file with make generate-stylesheets and commit that as well (as suggested by the DroneCI error message). ZerooCool : |
I have test a new pull request with the good code. I can not finalize. |
I install NODE.js and NPM cd gitea-local-depot/ npm ERR! A complete log of this run can be found in: I don't no how i can push my patch for " README WordPress the code is overflowing " In this file :
Can you add this patch please, push it on the deposit, because, I can not do it. You can see that the WordPress README is beyond the scope, so this patch seems to be necessary and answer to this problem. Using overflow keeps line numbering, so should not generate edge effects. Thank you for pushing this proposal, to be able to close this issue. |
https://codecov.io/gh/go-gitea/gitea/pull/6696/diff?src=pr&el=tree-more It must be checked that the lines are always correctly numbered for the PHP files for example, if that leads to line breaks. If everything is ok for viewing the WordPress README file that no longer floats. If the numbering was not affected by the change for PHP files. Then the issue is resolved and can be closed. |
@ZerooCool issue will be automatically closed when PR is merged |
Yes |
I can not install Gitea from Github on Debian. I followed another tutorial that refers to the official deposit from the site Gitea, to get to install Gitea: I thought that on the 24th the fix for no longer having the contents of the WordPress README coming out of the window had been fixed. The problem persists with the version I loaded on Gitea. I'm definitely not sure if the fix has been made on Github, and will it be carried also to the loading package on the Gitea official website. It's really a simple CSS problem. Can you add the fix? In this file :
|
Hi all, I am not by any means a CSS guru 😆 but shouldn't it be
Whilst having the scrollbars always visible it looks somewhat odd: Having the scrollbars only visible when content is clipped it looks way better when it is not (at least for me) and fullfills its job in case of overflowing content also: Sidenode: I am running gitea in a docker conatiner on the latest tag - currenbtly running version |
@kimpenhaus should be fixed now in latest version |
Hi, i need help for a fixe.
Can you see a page with the README file from WordPress ?
As you can see, the code is overflowing.
I tested different CSS property but I can not patch this problem.
It does not work with word-break or overflow
I then tried to replace from the browser, the html PRE tag DIV and the rendering is consistent.
Can you tell me if another way of doing things is possible in CSS, if not, can you tell me or find this PRE tag in the source code of GITEA, in order to correct it? Can you take into consideration my remark, and, bring a fix for this problem?
The text was updated successfully, but these errors were encountered: