Language…
6 users online: anoMaly666, anonimzwx, DanMario24YT, Gamet2004, Neuromancer, Saela - Guests: 264 - Bots: 328
Users: 64,795 (2,378 active)
Latest user: mathew

#80: A Different Spoiler Button

Link Thread Closed

New FeatureResolved

+1 to this

Spoilers working like that do the job better in my opinion. That would also work as a separate option besides the current spoiler, just for the sake of people who still prefer it.
Layout made by MaxodeX
2021 TRENO vibe check thread
I also support this. I'll work on it as soon as possible, but I likely won't have time for it until Saturday.

My plan is to implement this as a [collapse] tag. It expresses the purpose just as clearly and we'd keep backwards compatibility with posts using the old [spoiler] tag.

Speaking of the current spoilers, are they still broken on iOS? I have absolutely no way to test them and I'm not sure why they don't work, but it would still be nice to know. Anyhow, this isn't related to this issue.
Collapsibles have got the advantage that you can hide a large block of a text which might be useful for a larger code without using pastebin and similar sites. Another advantage is that you can pack multiple collapsibles inside another which doesn't work as much with the hover spoiler because the latter reveals every spoiler which you can avoid with the button.

Which also means, colappsibles should have the possibility to attach a name and uses by default "show" or "collapse" and "hide".
Originally posted by MarioFanGamer
Which also means, colappsibles should have the possibility to attach a name and uses by default "show" or "collapse" and "hide".

I considered bringing this up in my previous post, but I didn't because it's a feature which should very obviously exist, too.
Isn't this the way the talkhaus does its spoiler button?

Regardless, I'm on board.
                                                                                                                  
                              
At first, I got lazily practical and tried using a <details> element for this. Then I realized that our dear lord and savior Microsoft Edge (and Internet Explorer, which the site is also supposed to support) doesn't support it, so that was the end of that idea. Then I realized the HTML filter doesn't support IDs on elements - and for good reason, so a conventional checkbox hack wouldn't work, either.



This issue is now resolved. It will be closed if nobody replies with the feedback or complaints in the next few days.

Anyways, good job!
Check out Team Hack Fix/Translations' thread full of fixed and translated SMW hacks!

Wanted Permabanned or Dead by new staff team
Originally posted by Super Maks 64

where's my prize

Originally posted by Telinc1
(because I, for no particular reason, don't like things feature completely break with no JavaScript)

I also try to follow through this rule but, sometimes you just have to admit it's not possible. Besides, the checkbox way to do collapsible boxes actually has lower browser compatibility than the JavaScript way so, yeah.
Originally posted by RanAS
You're not the only one who tried.
I have a Discord server as well! (by joining, you agree to the rules)
-----
Basically, I believe in peace and bashing two bricks together.

I tried too, I thought it was a bug and thought to post about it
until I reached the end...


But it works very
--------------------
C'mon, man, I try my best.
これは「なにか」ですわ
SAN値!ピンチ!
Originally posted by RanAS
I also try to follow through this rule but, sometimes you just have to admit it's not possible. Besides, the checkbox way to do collapsible boxes actually has lower browser compatibility than the JavaScript way so, yeah.

Both arguments are so good that I can't even imagine how to respond. To be perfectly honest, the solution is just a little overengineered for no good reason, but that's just the way I am. JavaScript would be more compatible than the checkbox hack (which relies on CSS 2.1 selectors) but both would work in IE11, which is the only version we aim to support.

Anyway, nobody has complained about this so far, so I'm closing the issue for now. If you have more feedback, feel free to contact me.

New FeatureResolved

Link Thread Closed