For my part, I think there’s a bug and a feature here. We can disagree on semantics but I do want to explain how we’re looking at this so you understand what comes next here, given how important spoilers are to you and your community.
The bug is that when you try to apply a spoiler inline and across blocks, the paragraph breaks are removed (in rich text mode) and added to (in Markdown mode):
Rich text:
Markdown:
I agree this isn’t a pleasant experience. We can fix that bug, but what that will look like is either:
- Two separate spoilers, one on each line, that have to be clicked separately to reveal
- A single spoiler, but the selected content will be forced into its own block
The feature request is to support a single spoiler that can start inline and span multiple blocks, and then be revealed with a single click. That is not how spoilers were designed to work.
The reason I’ve asked about your use case is to assist with both fixing the bug and understanding the importance of the feature. We typically see spoilers either inline or as blocks, so I’m wondering if there are particular situations where the inline + block spoiler comes into play. That helps us get to know how you use Discourse better and understand how solving this could help you (and others who recognize their own community’s needs in what you share here).