Make check boxes clickable in issues

[troygeiger]

• Gitea version (or commit ref):1.8.2
• Git version:
• Operating system:All
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

Would it be possible to have the check boxes clickable in issues where the user is assigned or has permission to edit; like the functionality in GitHub?
...

Screenshots

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[cuzzea]

Any update on this? Would love to see it on.

[lunny]

Noboy are working on this.

[lordyavin]

It is a pain the ass to edit a comment to check thing from a todo list. Please schedule this issue for the next milestones.

[zeripath]

This is actually the kind of issue that a small bounty might be able to spur development on.

[davidak]

It's even worse. You can check boxes after you edited the comment, but it's lost when you reload the page. I would consider that a bug.

https://peertube.social/videos/watch/4be6219e-059d-4650-92cf-f0411f343b47

[zeripath]

PRs are welcome.

[viceice]

I've written a small greasemonkey / tampermonkey script to make gitea checkboxes clickable, see https://github.com/viceice/UserScripts/blob/master/gitea.cb.helper.js 🙃

[j2L4e]

There's a PR in the making.

A proper implementation needs a prop on the checkbox that states its position in the raw text. This needs to be done on the go side of things. As I haven't written a single line of go in my life and am, frankly, unwilling to dig into it right now, I'd highly appreciate if someone could do it for me so I can take care of the remaining JS stuff.

from #14258 (comment):

Does attaching a data-raw-position-start prop to the rendered checkboxes seem feasible to you? Somewhere around here?
https://github.com/go-gitea/gitea/blob/master/modules/markup/markdown/goldmark.go#L359
I'd expect the AST node to hold information about its origin (i.e. position in raw text)

If all checkboxes have that info attached replacing them becomes trivial and avoids brittle client-side parsing shenanigans.

[viceice]

@j2L4e I saw the pr after i finished my script 😅

[silverwind]

Github also allows to re-order task list items through a small drag handle on the left. I think this is also something we could implement via the sortablejs dependency that is already present.

[kdumontnu]

Bounty added!

If you'd like to promote this, please add

[![Bountysource](https://api.bountysource.com/badge/issue?issue_id=74933799)](https://www.bountysource.com/issues/74933799-make-check-boxes-clickable-in-issues)

To the Issue summary