Skip to main content

Timeline for New Feature: Table Support

Current License: CC BY-SA 4.0

11 events
when toggle format what by license comment
Dec 29, 2020 at 9:26 comment added TheMaster @HamVocke Would allowing inline spoliers using say >!spoiler text!< = <span>spolier text<span> help? I came across this and posted a Feature Request here
Dec 11, 2020 at 15:57 comment added Tech Expert Wizard I agree with @SonictheK-DayHedgehog . I don't think someone would really need to put a spoiler into a table. It doesn't really make much sense. It's just fun(ny) lol.
Dec 11, 2020 at 15:56 review Suggested edits
Dec 11, 2020 at 16:38
Dec 4, 2020 at 20:06 comment added Ham Vocke StaffMod @mindstormsboi mixing HTML and Markdown allows you to break out of some limitations but will sooner or later get you in trouble regarding other edge cases. There's another answer here outlining some of the things you can do with Markdown tables and HTML. Personally, I wouldn't encourage mixing HTML and Markdown since we know results can be hard to predict.
Dec 4, 2020 at 15:39 comment added mindstormsboi @HamVocke "Block-level elements like blockquotes won't work in Markdown tables..." Wait a minute, I think I found a workaround by using the blockquote HTML tag. Doesn't seem intentional, should I post this as an answer to this question?
Dec 4, 2020 at 7:45 comment added Ham Vocke StaffMod @TylerH I disagree. Forking Markdown would be a maintenance nightmare and we just took a step in the opposite direction with the CommonMark migration. Not allowing block-level elements inside tables is not an oversight. If you want to have a concise table syntax, you simply can't allow things that allow e.g. code blocks or blockquotes without running into conflicts. Tables rely on line breaks to mark the end of a row, blockquotes and code blocks allow line breaks as part of their content. Tables with line breaks within its cells would hardly be usable.
Nov 30, 2020 at 14:36 comment added TylerH @HamVocke I understand what you mean, but it's hard to call this 'by design'. It's more like markdown just doesn't support it, not that they intentionally chose for them to not work. This is one of the few cases where forking from Markdown is highly called for.
Nov 27, 2020 at 8:08 comment added Ham Vocke StaffMod Yep, this is definitely by design. Block-level elements like blockquotes, code blocks or spoilers won't work in Markdown tables.
Nov 27, 2020 at 8:07 history edited Ham VockeStaffMod CC BY-SA 4.0
added 21 characters in body
Nov 26, 2020 at 21:33 comment added Sonic the Anonymous Hedgehog I think this is more of a feature request than a bug. It seems that tables only support the same mini-Markdown features used in comments and bounty remarks.
Nov 26, 2020 at 21:21 history answered Ollie CC BY-SA 4.0