Skip to content
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 starting with a > are stored but automatically hidden #33869

Closed
jonasrosland opened this issue Mar 13, 2025 · 2 comments · Fixed by #33870
Closed

Comments starting with a > are stored but automatically hidden #33869

jonasrosland opened this issue Mar 13, 2025 · 2 comments · Fixed by #33870
Labels
Milestone

Comments

@jonasrosland
Copy link

Description

If you create an example comment like this:

this is a test comment

Then then comment is stored, can be retrieved by the API, but us hidden in the webui:

Image Image

It's apparently being hidden by the tw-hidden class:

<div id="issue-6264-raw" class="raw-content tw-hidden">&gt;
this is a test comment</div>

This can be verified here: https://demo.gitea.com/jonasrosland/testrepo/issues/1

Gitea Version

1.23.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Using the default docker compose file

Database

None

@wxiaoguang
Copy link
Contributor

-> Fix markdown render #33870

@lunny lunny closed this as completed in 8a0f7f0 Mar 13, 2025
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Mar 14, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Fix go-gitea#33869, some code block is moved to make it easier to test.

Added a new test
@wxiaoguang
Copy link
Contributor

1.23 nightly is ready (it is a stable release and will be 1.23.6 soon), it contains that fix. The reason is that some markdown texts would trigger a nil-pointer access, then backend failed to render the content.

@lunny lunny added this to the 1.23.6 milestone Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants