View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0022180||mantisbt||markdown||public||2017-01-12 07:12||2020-05-24 05:13|
|Priority||normal||Severity||major||Reproducibility||have not tried|
|Summary||0022180: Markdown issues following implementation in #17920|
This is a parent issue to regroup various issues with Markdown rendering, that must be fixed prior to release (hence setting severity to major, so it shows on the blockers list)
|Tags||No tags attached.|
|parent of||0022164||closed||joel||Font for quoted string in markdown is too large|
|parent of||0022167||confirmed||joel||Markdown: poor handling of legacy multi-level quoted text|
|parent of||0022179||closed||joel||Markdown is eating apostrophe / single quote|
|parent of||0022175||closed||joel||Markdown converting '<' within backticks to & lt;|
|parent of||0022172||closed||joel||Markdown not displaying single line breaks|
|parent of||0022181||assigned||joel||Markdown different rendering between inline code (single backtick) and ``` blocks|
|parent of||0022190||assigned||joel||Markdown markup should be done with CSS classes, not inline styles|
|parent of||0022204||closed||vboctor||News headlines are parsed with markdown, though they should not be|
|parent of||0022231||assigned||joel||Fix unit tests for markdown|
|parent of||0022242||closed||dregad||Markdown converting '&' within links to '&'|
|parent of||0022246||closed||joel||Markdown is converting '&' signs to (ampersand[amp;]) inside code block or backtick as well|
|parent of||0022344||confirmed||joel||Markdown mismatches code start/end|
|parent of||0022333||closed||joel||Markdown starts heading in the middle of a line|
|parent of||0022315||assigned||joel||Markdown converts " to " within code blocks and inline code|
|parent of||0022320||assigned||joel||Don't expand issue ids into URLs within code blocks|
|parent of||0022485||assigned||joel||Increase spacing before ``` blocks|
|parent of||0024241||assigned||dregad||$g_html_valid_tags are not rendered if Markdown is enabled|
|parent of||0024628||assigned||dregad||Double quotes " and lesser than sign < are shown as HTML entity within Markdown code blocks|
|related to||0017920||closed||joel||Native markdown support|
|related to||0022428||closed||vboctor||CSV and Excel exports with markdown on|
|Not all the children of this issue are yet resolved or closed.|
The markdown feature is OFF by default. I don't see any markdown fixes as blocking. We can mention in the announcement that the markdown support is experimental and off by default. It is good to get more people playing it with and providing feedback.
OK, I forgot it was off by default. Feel free to lower severity then.
@dregad, can we delete this issue in favor of "markdown" category and severities on such issues? We can't resolve it since it has child issues that are not resolved.
I'd rather keep it. I like having a parent issue, for the following reasons:
Speaking of markdown category, I'm wondering if would not have been better managed with a tag, which is more horizontal as we can have markdown issues not only in the tracker, but also in e-mail notifications, RSS, etc.
...unless they belong to another sub-project. In that case all grouping is lost there. Selecting the parent project doesn't help either because 'atoms' in the list are separate projects regardless of their inter-project hierarchy, and despite the fact that they can and often do all share the same (i.e. inherited from parent) versions.
Of course it would be a nice feature request to get Roadmap and Change Log to work horizontally on the selected project level instead of mercilessly drilling downstream from the selected level. Should I create a separate issue for it?
You can if you want to, but don't get your hopes too high of seeing it implemented anytime soon ;-)