Quoted text is breaking because of curly quote conversion

We are running 2026.7.0-latest.

A user (moderator) is reporting that whenever they quote a second+ block of text the quote mechanism is breaking. Here is an example of what gets added to the composer:

[quote="Biguser, post:437, topic:42137”]
The quoted text bla bla bla
[/quote]

The problem is caused by the close quote character being converted to a curly quote. (Look carefully above. Took me a while to see it)

The thus broken bbCode is rendered simply as text. when they publish.

They are on a Macbook using the DuckDuckGo browser. They cannot reproduce on Safari and I can’t reproduce it at all. So far no other user has reported the issue, but I have a vague recollection of seeing someone post similar broken code previously so I’m 99% sure it isn’t just this user.

The problem persists when they try in safe-mode.

Hey @one1, thanks for the detailed report and for trying safe mode!

This looks like it could/will be a browser-level autocorrect behaviour — DuckDuckGo’s browser (which is based on WebKit but with its own text handling layer) may be converting the closing " in the BBCode tag to a curly quote before Discourse even sees it. That kind of substitution would break the quote syntax exactly as you’re describing.

Since it doesn’t reproduce on Safari and no other users have reported it, this is likely specific to DuckDuckGo browser’s text input handling, which is outside of what we’re able to fix on our end.

The best path forward for your moderator would be to use a mainstream browser like Safari, Firefox or Chrome. Alternatively, they could check if DuckDuckGo browser has a setting to disable smart/curly quotes.

This seems similar to Smart quotes breaking Quote template

Credit goes to our mod for making me a screen cast so my brain could finally see what was happening.

And thank you for your instant reply. I will pass all that on to them. And be on the lookout for it happening to anyone else.

Oh wow. I think that is exactly it. I’m sorry I didn’t find that first. Thanks!