There are multiple posts (mainly WikiPosts) that use the SPOILER BBCode for providing collapsible sections that are not necessarily spoilers.
Here are some examples:
As you can see, these examples use the SPOILER code incorrectly. Instead of using them for spoilers, they are used to make the posts easier to navigate. However, the SPOILER code always adds a "Spoiler" prefix to the show/hide link, as shown here:
I think that adding a seperate code COLLAPSE would be a good idea. It would function the same as the SPOILER code except that there is no "Spoiler" prefix added to the show/hide links.
Here are some examples:
Sign In With Apple - Supported Apps & Sites
It’s been a few months since the release of iOS 13 and Sign in with Apple is having a very slow rollout. While some major apps like Adobe Lightroom and Photoshop, TikTok and Wordpress have recently added it, most of the top apps have yet to support Apple’s sign in. That might be about to change...
forums.macrumors.com
The PowerPC Debian Wiki
Mac OS X Tiger was released in 2005, its final security update being in 2009. Mac OS X Leopard was released in 2007, given its very last security update in 2011, and is the ultimate version of Mac OS X compatible with the PowerPC architecture, effectively marking the entire family EOL, even for...
forums.macrumors.com
As you can see, these examples use the SPOILER code incorrectly. Instead of using them for spoilers, they are used to make the posts easier to navigate. However, the SPOILER code always adds a "Spoiler" prefix to the show/hide link, as shown here:
Hello World!
I think that adding a seperate code COLLAPSE would be a good idea. It would function the same as the SPOILER code except that there is no "Spoiler" prefix added to the show/hide links.
Last edited: