Make check boxes clickable in issues #3406

@stale[bot] commented on GitHub (Jul 31, 2019):

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.

@stale[bot] commented on GitHub (Jul 31, 2019): 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.

GiteaMirror commented

@cuzzea commented on GitHub (Nov 21, 2019):

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

@cuzzea commented on GitHub (Nov 21, 2019): Any update on this? Would love to see it on.

GiteaMirror commented

@lunny commented on GitHub (Nov 21, 2019):

Noboy are working on this.

@lunny commented on GitHub (Nov 21, 2019): Noboy are working on this.

GiteaMirror commented

@lordyavin commented on GitHub (Apr 28, 2020):

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.

@lordyavin commented on GitHub (Apr 28, 2020): 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.

GiteaMirror commented

@zeripath commented on GitHub (Apr 30, 2020):

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

@zeripath commented on GitHub (Apr 30, 2020): This is actually the kind of issue that a small bounty might be able to spur development on.

GiteaMirror commented

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

@davidak commented on GitHub (Jun 7, 2020):

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.

@davidak commented on GitHub (Jun 7, 2020): 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

GiteaMirror commented

@zeripath commented on GitHub (Jun 7, 2020):

PRs are welcome.

@zeripath commented on GitHub (Jun 7, 2020): PRs are welcome.

GiteaMirror commented

@viceice commented on GitHub (Jan 12, 2021):

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 🙃

@viceice commented on GitHub (Jan 12, 2021): 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 🙃

GiteaMirror commented

from https://github.com/go-gitea/gitea/pull/14258#discussion_r552540733:

@j2L4e commented on GitHub (Jan 12, 2021):

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.

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.

@j2L4e commented on GitHub (Jan 12, 2021): 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 https://github.com/go-gitea/gitea/pull/14258#discussion_r552540733: > 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.

GiteaMirror commented

@viceice commented on GitHub (Jan 12, 2021):

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

@viceice commented on GitHub (Jan 12, 2021): @j2L4e I saw the pr after i finished my script 😅

GiteaMirror commented

@silverwind commented on GitHub (Apr 13, 2021):

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.

@silverwind commented on GitHub (Apr 13, 2021): 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.

GiteaMirror commented