Markdown Rendering Issues on npmjs.com about marky-markdown HOT 8 CLOSED

thanks so much for filing :) and extra thanks for the great test module!

from marky-markdown.

"Incorrect Code Indents" and "Tabs Are Rendered Extremely Wide" might be candidates for marky fixes; essentially the problem there is that browsers are rendering \t characters with traditional eight-character width. Github is replacing them with four spaces. We should probably look around to determine under which circumstances they make this substitution (it could just be that tabs in leading whitespace get replaced) and follow suit.

"Incorrect Nested List Indents", "No Space After Lists", and "Tables Centered By Default" look to me like newww CSS issues, as opposed to markdown-to-HTML errors.

from marky-markdown.

Thanks @revin -- I'll resubmit "Incorrect Nested List Indents", "No Space After Lists", and "Tables Centered By Default" as CSS rendering issues in the https://github.com/npm/newww repo.

from marky-markdown.

thank you so much @jhuckaby ! i was about to do this. so awesome that you already have :)

from marky-markdown.

My pleasure @ashleygwilliams 👍

from marky-markdown.

@jhuckaby ditto on the thanks, I really like the idea of having a markdown torture test module specifically there to look for rendering bugs. (And sorry to keep bouncing you around between issue trackers!)

from marky-markdown.

Haha, no problem @revin -- happy to help. I'll continue to add test cases to my torture test module as I find them 😉

from marky-markdown.

The marky-specific parts of this were fixed in #127; closing

from marky-markdown.