You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I'm not mistaken, ordered lists starting with any positive number will have the start='N' attribute, but this is not the case when starting a list with 0, it will simply start it at the default 1.
Is this expected behavior based on the spec (I did not see any rules prohibiting it, but I could be wrong), and would you consider adding it as a feature? I think it would be beneficial seeing how especially in areas related to computing often indexes begin with a 0.
The text was updated successfully, but these errors were encountered:
I've re-read the spec and came to the same conclusion as you - 0. is definitely a valid ordered list marker, so the start attribute should be set to 0. I'll work on implementing a fix for this.
I've also filed an issue "upstream" with the JS implementation that we're based off: commonmark/commonmark.js#10
If I'm not mistaken, ordered lists starting with any positive number will have the start='N' attribute, but this is not the case when starting a list with 0, it will simply start it at the default 1.
Is this expected behavior based on the spec (I did not see any rules prohibiting it, but I could be wrong), and would you consider adding it as a feature? I think it would be beneficial seeing how especially in areas related to computing often indexes begin with a 0.
The text was updated successfully, but these errors were encountered: