Quoted markdown lists don't render correctly. Why Does Discourse keep breaking stuff that used to work?
-
Continuing the discussion from Lists in Quotes:
Test list for bug report.
- This
- is
- a
- list
See?
Self explanatory.
-
Off to meta.d …
-
And I'm back!
Markdown lists don't render correctly in quotes
When quoting a list, it doesn’t render correctly in the quote. Here is a simple list: This is a list It will be quoted in a reply to this post to demonstrate the formatting bug.
-
An epic INB4 CLOSED : WONTFIX
-
I jeffed 2 posts to an existing topic: Lists in Quotes
-
I jeffed a post to an existing topic: Lists in Quotes
-
aaaaaand CLOSED-DUPLICATE
that didn't take long
-
- This
- breaks
- too,
- guys.
- I
- guess
- they
- will
- just
- ignore.
1. This
2. breaks
3. too,
4. guys.
5. I
6. guess
7. they
8. will
9. just
10. ignore.
-
This post is deleted!
-
And it's apparently a "feature request" too....
Dischorse.
-
aaaaaand CLOSED-DUPLICATE
that didn't take long
Not sure if it’s a actual duplicate, though. @abarker’s bug was about full quoting, but the linked bug report seems to be about partial quoting...
-
this is discourse.... there's a difference?
i of course disagree with the closure, but i'm not a discodev. (i just like to break discourse)
-
aaaaaand CLOSED-DUPLICATE
that didn't take long
Reopened:
https://meta.discourse.org/t/markdown-lists-dont-render-correctly-in-quotes-take-2/26030?u=abarker
Yes, I read the "duplicate" topic. No, it isn't really a duplicate.
-
well at least @zogstrip liked this one.
any bets on how long it takes to get closed and if it will be fixed or not?
-
this is discourse.... there's a difference?
Yes, there is a difference between the two quoting methods.[1] When you use full quote, you get the raw of the post you are quoting. The raw might get munged a bit when it's shoved into the text area (see image tags), but you do get the raw. When you do a highlight and "quote reply", you get an HTML sanitized version of the post you are quoting. It strips out the formatting, and sometimes you even lose "excess" whitespace such as line returns.
###Examples
####Full Quote1. This
2. breaks
3. too,
4. guys.
5. I
6. guess
7. they
8. will
9. just
10. ignore.####Quote Reply
This
breaks
too,
guys.
I
guess
they
will
just
ignore.Notice how the list is missing from the second quote?
[1] Disclaimer: Information inferred from reading meta.d
-
well at least @zogstrip liked this one.
any bets on how long it takes to get closed and if it will be fixed or not?
Oooh, he sent me a PM too! Let's see what it says!
Oh, just saying I could have PM'd him to reopen it. Guess this means he agrees with my argument that it isn't a dup.
-
any bets on how long it takes to get closed and if it will be fixed or not?
Depends on if it is in the sanity budget.
-
Oh, just saying I could have PM'd him to reopen it.
Reply:
"But the method I chose had a greater guarantee attached."
-
Reply Option 2:
I don't belgium around with tier 1 support.
-
Reply:
"But the method I chose had a greater guarantee attached."Or: “I couldn’t find the
Reopenbutton on your bug tracker”.
-
He is TL4+ over there so he could have simply merged the two topics..
Filed Under: About as much work as writing a PM saying "write me a PM"
-
He is TL4+ over there so he could have simply merged the two topics..
Merging topics is not a thing in Discourse.
See, when you try to move an OP the OP stays, and a copy of the OP is created in the target location.
-
Oh... yeah... Discourse... WHAT?
Filed Under: I remember you guys making multiple One Post about this now that you mention it...
-
Yes, there is a difference between the two quoting method
i meant between CLOSED FIXED and CLOSED WONTFIX
:-P
-
i meant between CLOSED FIXED and CLOSED WONTFIX
:-P
How was I supposed to get that from context?
-
How was I supposed to get that from context?
at the time i thought it was obvious. rereading it now it appears to have been a complete non-sequitur.
-
-
non-sequiter
i sit corrected....
(not google corrects spellaring before defining)
-
i meant between CLOSED FIXED and CLOSED WONTFIX
The difference is that one is much more common than the other. Identifying which is the more common is left as an exercise for the reader.
-
-
In today's edition of Reading Is a Barrier to Posting, by @codinghorror...
-
As he didn't instantly Jeff™ the topic, I wasn't sure whether he was trying to be funny or being serious.
-
Or maybe topic locking is broken? :D (why are the smileys so awful...)
-
It's probably the only feature Jeff tests.
-
-
The difference is that one is much more common than the other. Identifying which is the more common is left as an exercise for the reader.
Is there any correlation with "The bug has been fixed"?
How about "The bug will be present next month"?
-
With Discourse, those are synonymous.
