Users reported issues with spoiler blur functionality in the new rich text composer mode. donaldsoncd noted that spoilers appear as single-line text boxes without blur during composition, unlike the final rendered post. Shauny added that inline spoilers (within sentences) are no longer possible, forcing spoilers into separate paragraphs — a usability regression. sam confirmed the bug, clarifying that raw mode still works and that the rich text mode incorrectly escapes spoiler tags as \[spoiler\]. Shauny emphasized the importance of inline spoilers for their fiction forum, arguing that requiring raw mode defeats the purpose of a user-friendly rich text editor. donaldsoncd also reported a mobile-specific issue: applying spoilers collapses the keyboard unexpectedly. renato later announced the main issues were fixed. donaldsoncd confirmed fixes on mobile, including blur and keyboard behavior. However, Shauny still experienced block-style spoilers on their site, suspecting an outdated version; renato asked them to test on Meta, which Shauny couldn’t reproduce, suggesting their forum may need another update.
Not sure if this a bug or a feature request.
In the new rich text composer mode if you add a spoiler to some text, you don’t see a spoiler blur. Instead, you see a text box with all the text put into a single line.
Ideally, I think the spoiler blur should appear the same way that it is rendered after posting.
Here’s an example.
Before applying the spoiler blur:
After applying spoiler blur (note the paragraph is on one line now in a box with no blur):
Final render upon posting:
I’d also add here that it is no longer possible to spoiler parts of a sentence, it makes the spoiler a new paragraph, which is a step backwards in usability.
Note … everything that was possible remains possible. You can always flick to raw mode.
I confirm that typing [spoiler]something[/spoiler] is currently not working as expected in the rich text composer.
Instead of \[spoiler\]something\[/spoiler\] it should result in [spoiler]something[/spoiler]
We will look at this.
Whilst that is true, it would be best if the Rich Text mode worked the same as it used to, so you could have inline spoilers. Otherwise it’s just confusing for people - this is supposed to be easier to use but now I have to tell people to switch to a different mode to do spoilers.
(Mine is a discussion forum about fiction stories and the spoiler button is heavily used!)
This is a temporary situation, we will sort this out
Additional related feedback from my users and that I can confirm. Immediately you apply the spoiler blur on mobile, it collapses the keyboard on mobile in a way that is weird. Basically, you land on this view right after applying it (notice the composer still being open, but no keyboard visible:
The main issues have been fixed, let us know if you find anything else.
Just tested on mobile and it now seems to be working fine for both blurring paragraphs and parts of a sentence. Also the keyboard collapsing issue has gone away. Thank you very much! 
It does not seem to be fixed on my site. It still puts spoilers on its own line (block instead of inline).
Is there another patch I need to install?
The screenshot doesn’t seem to be from the current version. Can you reproduce it here on Meta?
I can’t, no.
We updated our forum 20 hours ago though. But maybe it was just before this fix. I’ve asked our hosts to update it again.
This topic was automatically closed after 2 days. New replies are no longer allowed.
