Task list can't be resolve, is there a bug or a feature?

[driftluo]

when I use in brower, marked.js is in marked project's lib folder

<script src="js/marked.js"></script>

> marked('- [ ] x')
"<ul>
<li>[ ] x</li>
</ul>
"

and there is same issue on https://github.com/8fold/marked
@8fold

[joshbruce]

Do you mean bower or browser? Not sure I follow exactly what's expected versus what's being received.

[driftluo]

browser

[joshbruce]

The expectation would be something more like this, yeah:

<ul>
  <li><input type=”checkbox”><label>Hello</label></li>
</ul>

Yeah?

[driftluo]

In github, it will be like this:

<ul class="contains-task-list">
  <li class="task-list-item">
  <input class="task-list-item-checkbox" disabled="" id="" type="checkbox"> Hello</li>
</ul>

[joshbruce]

@driftluo: Thanks for that. Think we would leave out the classes. Basically, give back the input and type. From an HTML perspective, I don't place a lot fo form controls outside of forms; so, is the GitHub markup accessible (what's the experience like for a blind person, for example).

@UziTech: Thoughts?

[UziTech]

I'm not sure that would be in scope for this package.

Maybe if we add extensions like markdown-it. Seems like you would want to use markdown-it-checkbox.

[fboes]

I added a simple fix for this locally, without altering marked:

marked('- [ ] x')
  .replace(/(<li>)\[ \](\s)/g,'$1<input type="checkbox" />$2'))
  .replace(/(<li>)\[x\](\s)/g,'$1<input type="checkbox" checked="checked" />$2');

I am also not sure if it is a good thing to change this behavior. Some implementations might depend on how marked is currently working (like mine 😁 ).

[joshbruce]

See #982