View Issue Details

WikiRelated ChangesetsJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0022190mantisbtmarkdownpublic2017-01-13 03:352022-09-03 06:09
Reporterdregad Assigned Tocommunity  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Product Version2.1.0 
Target Version2.26.0Fixed in Version2.26.0 
Summary0022190: Markdown markup should be done with CSS classes, not inline styles
Description

As per discussion in https://github.com/mantisbt/mantisbt/pull/990#issuecomment-272044046

Using classes is preferable over the current use of hardcoded inline styles, as it would make changes in design easier, and allow admins to customize the CSS should they want to.

TagsNo tags attached.

Relationships

related to 0024233 closedatrol Markdown quoting rendered with broken HTML 
related to 0022181 assignedjoel Markdown different rendering between inline code (single backtick) and ``` blocks 
related to 0030919 assigneddregad Markdown processing code cleanup 
child of 0022180 new Markdown issues following implementation in 0017920 

Activities

joel

joel

2017-01-23 03:20

developer   ~0055258

PR: https://github.com/mantisbt/mantisbt/pull/1004
dregad

dregad

2022-09-03 06:09

developer   ~0066966

Fixed by PR https://github.com/mantisbt/mantisbt/pull/1841, thanks to @hotzeplotz

Related Changesets

MantisBT: master 3faaae32

2022-09-03 05:54

dregad


Details Diff		 Markdown processing code cleanup, step 1

This addresses step 1 (cleanup quotings) of issue 0030919.

Merge PR https://github.com/mantisbt/mantisbt/pull/1841		 Affected Issues
0022190, 0030919
mod - plugins/MantisCoreFormatting/MantisCoreFormatting.php Diff File
mod - plugins/MantisCoreFormatting/core/MantisMarkdown.php Diff File
add - plugins/MantisCoreFormatting/files/markdown.css Diff File
mod - plugins/MantisCoreFormatting/tests/MarkdownTest.php Diff File