# Rich Text: Checklist usability improvements

**URL:** <https://community.fibery.io/t/rich-text-checklist-usability-improvements/1957>\
**Category:** Bugs & Issues\
**Tags:** rich-text\
**Created:** [August 28, 2021, 5:23pm UTC](https://community.fibery.io/t/rich-text-checklist-usability-improvements/1957 "2021-08-28T17:23:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [August 28, 2021, 5:23pm UTC](https://community.fibery.io/t/rich-text-checklist-usability-improvements/1957/1 "2021-08-28T17:23:49Z")

</div>

Checklists in Rich Text fields have some quirks that make them unnecessarily cumbersome, compared to e.g. how Bulleted Lists work.

- When the cursor is at the beginning of a non-blank line, inserting a Checklist (by typing “/k ENTER”) creates a NEW empty Checklist BELOW the current line. It would be preferable to instead CONVERT the current line into a Checklist (as happens with Bulleted lists and everything else).

- When the cursor is at the _end of the line_ on the _last item_ of a Checklist, hitting DELETE does _not_ append/convert the following line into the current line (last Checklist item) as expected.

- Checklist items/lines cannot be converted into other paragraphs types (headings, bulleted lists, etc) without first changing them into a regular paragraph.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 28, 2021, 6:39pm UTC](https://community.fibery.io/t/rich-text-checklist-usability-improvements/1957/2 "2021-08-28T18:39:23Z")

</div>

While we’re talking about checklist improvements, I’d love it if they could be nested/indented! So many other tools allow this, and I find it extremely useful.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [August 28, 2021, 7:39pm UTC](https://community.fibery.io/t/rich-text-checklist-usability-improvements/1957/3 "2021-08-28T19:39:08Z")

</div>

Uh-oh, more Rich Text [divergence from vanilla markdown](https://community.fibery.io/t/pasting-html-in-rich-text-ignores-color-alignment/1937/3) 😂

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [August 28, 2021, 8:12pm UTC](https://community.fibery.io/t/rich-text-checklist-usability-improvements/1957/4 "2021-08-28T20:12:32Z")

</div>

Well, yes and no. 😄 Check lists are not supported either by the original Markdown spec nor by “Commonmark”, one of the more, er, commonly used reference specs. But they _are_ supported by the also widely-used “Github Flavored Markdown”, which I believe Fibery either uses, or at least conforms fairly close to. And that spec does indeed include nested checklists. 😁  
[https://github.github.com/gfm/#task-list-items-extension-](https://github.github.com/gfm/#task-list-items-extension-)
