this post was submitted on 27 Nov 2023
20 points (100.0% liked)

/kbin meta

4 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
20
submitted 10 months ago* (last edited 10 months ago) by Damaskox@kbin.social to c/kbinMeta@kbin.social
 

There's a chance that I have forgotten something or missed something.

But these are my finds, so far.

you are viewing a single comment's thread
view the rest of the comments
[–] e0qdk@kbin.social 3 points 10 months ago (1 children)

Ironically, that doesn't work for me at all. (I have seen other spoiler blocks recently though, so not sure why not.)

[–] Damaskox@kbin.social 3 points 10 months ago (1 children)

Is it browser-, operating system- or device-related?

I'm on Windows PC, Firefox, at https://kbin.social/

[–] e0qdk@kbin.social 3 points 10 months ago* (last edited 10 months ago) (1 children)

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.

[–] Damaskox@kbin.social 2 points 10 months ago

Hmm. Okay.

Yeah I'm no code savvy so let's hope they know more about it 😁