WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2024 Poal.co

390

View source to see what I mean.

  1. This is NOT #3.

And what's with the <P> tag inserted around the text in #3? It makes it display strangely. <LI> is already a block element. Why are we nesting block elements for text?

View source to see what I mean. > 343434. > 6545654. > 54343. This is NOT #3. And what's with the <P> tag inserted around the text in #3? It makes it display strangely. <LI> is already a block element. Why are we nesting block elements for text?

(post is archived)

[–] 0 pt (edited )

That's Markdown. You have to escape the character.

54343. This is NOT #3.

> 343434. 

> 6545654. 

> 54343\. This is NOT #3.
[–] 0 pt

That's Markdown. You have to escape the character.

Thanks. Seems like a bug in markdown, even if they think it's a "feature."

If the parser is going to keep track of the list numbering, what is the point of a syntax that requires a number? It's kind of stupid. The markdown syntax to trigger ordered lists should be something that isn't commonly typed in everyday conversation.

[–] 0 pt

This link will explain why the markdown behaves the way it does.

https://daringfireball.net/projects/markdown/syntax#list

[–] 1 pt

I know that it does. What I'm saying is that it's wrong for markdown to do it that way. It's a bug, just not a bug poal can do anything about.

[–] 0 pt (edited )

>1. That is odd. 2. Can you replicate the bug? 3. I never had that issue yet. 4. Please do not jinx me.