Open rghedin opened 1 month ago
📌 REPRODUCTION RESULTS
Replicated only with comments on Atomic sites without using a block-based comment box. I couldn't spot any quick fix other than extending the existing markdown parser used for comments.
📌 FINDINGS/SCREENSHOTS/VIDEO
📌 ACTIONS
Have you tried edit the comment to use HTML, @phcp? In my site, this workaround doesn't work either. (Although I'm not sure if it's due to some CSS mistake.)
Have you tried edit the comment to use HTML, @phcp? In my site, this workaround doesn't work either. (Although I'm not sure if it's due to some CSS mistake.)
Yes, it worked fine for me. I had to submit the comment, click Edit, and format it as an HTML list.
Could you go to Jetpack > Settings, search for "markdown", and ensure Markdown is enabled for comments? Once you turn that on, you should see Markdown being processed in your future comments.
Let me know how that goes!
It is, @jeherve. Markdown works fine in comments, except for lists.
Thanks for giving it a try! We'll need to look at how data is sanitized by WordPress when submitting a comment. I suspect some HTML, like list items, are getting stripped by WordPress, but we'll see what we can do to fix that!
Impacted plugin
Jetpack
Quick summary
When writing a comment, a list made of * or - not only doesn't render properly as a HTML list, but also hides those characters. (At least using default comment form.)
Steps to reproduce
A clear and concise description of what you expected to happen.
What actually happened
Item 1 Item 2 Item 3
Impact
Most (> 50%)
Available workarounds?
No but the platform is still usable
If the above answer is "Yes...", outline the workaround.
No response
Platform (Simple and/or Atomic)
No response
Logs or notes
No response