*banned 4 MarkDown love* @design_RG@social.cleverlibre.org

@khird @freemo

And I can confirm that in MS Edge Chromium, logged in and Dark Theme wide screen set, all is displaying perfect now too.

** That 'None' button is Golden!!** 😺

@freemo Geez !!!

You got it.

I went to Preferences, and it had no Stripping preference selected at all as you expected.

Selected None, Saved. And looking at the test post, it now displays ALL GOOD!!!

Hallellujah! Thank you... Seems that fixes the problem.

@freemo @hansw@mastodon.social @QOTO
Ah, I see, thank you.

It's odd that the Light theme displays properly, while the Dark Theme, wide screen shows this.

@freemo @hansw@mastodon.social @QOTO
I went back to Light Theme in the Private Window, and copied a screenshot of just the inner post.

The quoted block -- it's delimited by a BlockQuote, closed at the end of the text. Text highlighted in Blue.

@freemo @hansw@mastodon.social @QOTO

> Thing is if i cant replicate the issue its really hard to investigate. If i were on Rob's computer id pull up the inspection tool and look to see if the HTML has the right tags and what css it is seeing and rendering, but I cant do that from my end if the issue doesnt get replicated here

I copied and pasted the post html for that -- see if it helps. Sorry as it is messy,

https://pastebin.com/BcK8Nxnz

@hansw@mastodon.social @freemo @QOTO
I use Waterfox, which is a FF variant, most of the time for everything.

I did load the MS Edge just to confirm if it was browser specific or not.

Other add ons here : uBlock Origin, and others that I don't think should interfere.

Let's wait and see if something comes up, as it might be a extraneous thing.

Thank you! 😃

@hansw@mastodon.social @freemo @QOTO

Thansk for the clarification, Hans. Are you using the Light or Dark theme ?

The problem seems to be specific to the 'Dark Theme, wide screen' -- and it displays these '>' in both FF and MS Edge chromium here.

Light Theme displays proper Quote, with the vertical bar marking the quoted text.

@freemo @hansw@mastodon.social @QOTO

Yes, it's a strange thing -- and the fact it shows properly with one theme and not on the other adds to the mystery.

I am not using the Collapsed Mastodon, which could possibly have affected the instance's display.

Hans's post is a bit vague - I am not sure of exactly what he observed, he might be seeing it as I see on my screenshot -- **with the '>' multiline quote markers**.

Maybe Hans can confirm or clarify? Thank you! :)

@freemo @QOTO

> What happens if you use the dark theme in a private window?

I would have to log in to change the Theme. Can try. Will do.

Done -- and if I login it shows the whole topic with the Dark Theme, wide screen.

And the Quote marks display, not like it was in the Light theme, **but with the odd '>' multiline markers**.

Another screenshot attached. FF, Private Mode. Logged into account, Dark Theme, wide screen in use.

@freemo @QOTO

I thought it could be a Browser specific thing, but **I see the exact same result in MS Edge Chromium based**, if I login to my user account.

That renders using the Dark Theme, wide screen, same as I use in Firefox (Waterfox variant).

Loading the same link to a post in this thread as posted above, with the odd quoting format, displays perfect in a FF Private Window tab; the difference being that in this case it's using the Qoto default theme, the Light theme.

Screenshot attached.

@freemo @QOTO

Here's [a really nicely formatted Glitch-Social rendered post](https://muensterland.social/@rgx/104282268223925390).

Screenshot attached.

@freemo @QOTO
The webclient is the one displaying the '>' markings.

In general, **Markdown in Glitch-Social is the best rendered one** - showing heading sizes, quotes, a blank line after a quote block or a Heading2 title.

Pleroma has some glitches in those - like not showing larger text size for Headings as expected, and not showing a blank line after a heading and before the next paragraph as included in the original. (I filled a bug report about those on their dev site).

@freemo @QOTO

Yes -- the one just above, for example. https://qoto.org/@design_RG/105119371158013921

Screen captures in :
* Mastodon web client.
* and Pinafore attached.

@freemo @QOTO

> Ok thats interesting if your own markdown post isn’t rendering as markdown.. are you saying it doesn’t format it with the markdown when you post from a mobile client specifically. Or do you get this error from the web too?

The post I referred to and linked above was done in my laptop, FF browser using the mastodon web client.

It's odd that it did not format as expected.

The next post I wrote in Pinafore, also on the same browser, just one tab aside. The Bold and Italic did display, I did that specifically for testing.

Odd since posting from the web client previously for testing, earlier this week, was working fine.

***Regarding Quoted paragraph*** - it shows properly in Pinafore, not in masto web client.

Odd... 😃

@freemo
The one you are replying to yes, it rendered as expected.

The one with no formatting is my own, [further above, this toot](https://qoto.org/@design_RG/105119247687187651)

I found it odd how it did not show MD - I have it **setup as default for all toots in Mastodon Preferences**, so I don't have to worry about changing back and forth.

@QOTO

@freemo

> BTW - seems MarkDown formatting ins broken at the moment? (noticed in an earlier post in this thread; some bold and bold-italic only showing as asterisks, plain text). Adding a bit of format to test this, via Pinafore.

That *DID work in Pinafore*, although an earlier post in **web client** did not.

Edit : mixed results here, del/redraft to add comment. **Bold** worked as expected.

Quote paragraph did not, showing with ***multi-line '>' here***; I only used a single char at the begginning of paragraph quoted.

@QOTO

@freemo

Very nice that you are taking this on -- an enhancement to Fediverse features. Well done... 😃

BTW - seems **MarkDown formatting** ins broken at the moment? (noticed in an earlier post in this thread; some bold and bold-italic only showing as asterisks, plain text). Adding a bit of format to test this, via Pinafore.

@QOTO

@freemo

Ah, I see. ***Followers only*** would work, right? Yuo mentioned it as a possible **Private group** arrangement.

@QOTO

@freemo @QOTO >> Test post, ignore me.

Yep. Could try an unlisted or DM style post, it's what I do for markdown checking if a post is more complex (to see if all is well; then delete/redraft and change to normal privacy).

@QOTO