Fix checkbox rendering in issues #666

New Issue

GiteaMirror · 2025-11-02T03:32:20-06:00

GiteaMirror commented

2025-11-02 03:32:20 -06:00

Originally created by @mirhec on GitHub (Apr 25, 2017).

Gitea version (or commit ref): master
Git version: the version on try.gitea.io
Operating system: Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL): https://try.gitea.io/mirhec/test/issues/1
- No
- Not relevant
Log gist:

Description

You can create checkboxes via the [ ] brackets, but there always is a line break after the checkbox. The following issue-content

## Checkbox

- [ ] Test 1
- [x] Test 2
- [ ] Test 1

renders to

Originally created by @mirhec on GitHub (Apr 25, 2017). - Gitea version (or commit ref): master - Git version: the version on try.gitea.io - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL): https://try.gitea.io/mirhec/test/issues/1 - [ ] No - [ ] Not relevant - Log gist: ## Description You can create checkboxes via the `[ ]` brackets, but there always is a line break after the checkbox. The following issue-content ``` ## Checkbox - [ ] Test 1 - [x] Test 2 - [ ] Test 1 ``` renders to ![image](https://cloud.githubusercontent.com/assets/5173805/25386065/526304cc-29c6-11e7-9a94-8720a07f38c2.png)

GiteaMirror added the type/bug label 2025-11-02 03:32:20 -06:00

GiteaMirror closed this issue

2025-11-02 03:32:20 -06:00

GiteaMirror commented

2025-11-02 03:32:21 -06:00

@silverwind commented on GitHub (Apr 26, 2017):

They are wrapped by a bare <div>, which should probably just be removed.

Also, it'd be great if they were checkable and that these state changes would edit the underlying markdown (if the user has edit permission), but that's probably more complicated to realize.

@silverwind commented on GitHub (Apr 26, 2017): They are wrapped by a bare `<div>`, which should probably just be removed. Also, it'd be great if they were checkable and that these state changes would edit the underlying markdown (if the user has edit permission), but that's probably more complicated to realize.

GiteaMirror commented

2025-11-02 03:32:21 -06:00

@pree commented on GitHub (Apr 27, 2017):

This has probably something to do with #186

@pree commented on GitHub (Apr 27, 2017): This has probably something to do with #186

GiteaMirror commented

2025-11-02 03:32:21 -06:00

@kenogo commented on GitHub (Apr 11, 2019):

Is there a reason to keep the bullets next to the checkboxes? It seems like quite an unusual way to handle it. At least GitHub and GitLab both don't do it.

@kenogo commented on GitHub (Apr 11, 2019): Is there a reason to keep the bullets next to the checkboxes? It seems like quite an unusual way to handle it. At least GitHub and GitLab both don't do it.

GiteaMirror commented

2025-11-02 03:32:21 -06:00

@lunny commented on GitHub (Apr 11, 2019):

@kenogo please fire another issue to discuss that.

@lunny commented on GitHub (Apr 11, 2019): @kenogo please fire another issue to discuss that.

GiteaMirror referenced this issue

2025-11-02 06:57:14 -06:00

gitlab migrate mergerequests+issues fail #6479

Sign in to join this conversation.