Now I just need to find a convenient way to save this piece of code and copy-paste it whenever I need it 🤔
Honestly, I’d just suggest to add a button for it in the editor after the code one? I think it’s a common enough thing to use to warrant it. For every other formatting maybe a little link for a pop up or expandable that shows the remaining formatting rules, similar to how it was on old.reddit.
I’m poking around at it now. I’m guessing it’s probably something to do with JavaScript – which I block by default via NoScript. (That’s kind of odd though since I thought it was generating a /\ HTML block server side, but maybe it’s doing it on the client and I just happened to have JS unblocked when I saw it before?)
Edit: It looks like it is coming from this webpack’d JS file currently which I think is built from this JS source file; there is a handleSpoilers function defined which manipulates details/summary elements. Oddly, there is also PHP code for manipulating details/summary like I thought.
@ernest can chime in on if that’s a temporary thing or what, but yeah, it seems to not work for me because I block JavaScript.
Yo, that is so good to know!
Wish there was a link to some quick stylesheet guide that kbin supports when you write a comment. Haven’t seen this feature before.
I would guess it’s the capacity of masking text through markdown for spoiler purposes:
https://github.com/LemmyNet/lemmy/issues/104
masking text
Like this?
kbin does that just fine.
Oh my Deity how did you do that?!
I’ve been cursing enviously for days when I see a spoiler (system) I couldn’t use myself!
I didn’t get Lemmy’s style to work.
hidden text title
hidden text
::: spoiler hidden text title hidden text :::
test
Does this thing work?
sigh Finally.
Now I just need to find a convenient way to save this piece of code and copy-paste it whenever I need it 🤔
.
…except that when I wrote more text into this comment, the code broke 🤔
Upon further testing - if I edit a text, the spoiler stops working. When I update the page, the spoiler works again.
Indeed, I missed that case, thanks.
Honestly, I’d just suggest to add a button for it in the editor after the code one? I think it’s a common enough thing to use to warrant it. For every other formatting maybe a little link for a pop up or expandable that shows the remaining formatting rules, similar to how it was on old.reddit.
I wholeheartedly agree on the editor button!
deleted by creator
deleted by creator
Ironically, that doesn’t work for me at all. (I have seen other spoiler blocks recently though, so not sure why not.)
Is it browser-, operating system- or device-related?
I’m on Windows PC, Firefox, at https://kbin.social/
I’m poking around at it now. I’m guessing it’s probably something to do with JavaScript – which I block by default via NoScript. (That’s kind of odd though since I thought it was generating a /\ HTML block server side, but maybe it’s doing it on the client and I just happened to have JS unblocked when I saw it before?)
Edit: It looks like it is coming from this webpack’d JS file currently which I think is built from this JS source file; there is a
handleSpoilers
function defined which manipulates details/summary elements. Oddly, there is also PHP code for manipulating details/summary like I thought.@ernest can chime in on if that’s a temporary thing or what, but yeah, it seems to not work for me because I block JavaScript.
Hmm. Okay.
Yeah I’m no code savvy so let’s hope they know more about it 😁
Yo, that is so good to know!
Wish there was a link to some quick stylesheet guide that kbin supports when you write a comment. Haven’t seen this feature before.
It just got added last week. This is the post demoing it in the devlog: https://kbin.social/m/kbinDevlog/t/651148/RTR-22-Further-improvements-interspersed-with-code-refactoring
deleted by creator