this post was submitted on 25 Nov 2024
484 points (98.0% liked)

Microblog Memes

6037 readers
2134 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 7 points 1 month ago (1 children)

@[email protected]

FYI Tesseract does not render nested spoilers like Lemmy UI, Thunder, and Voyager do. Tesseract requires an end tag for each start tag. For what it's worth, Jerboa doesn't seem to support nested spoilers either way.

Spoiler 1Test
spoiler Spoiler 2 Test
Spoiler 3Test
::: :::

Spoiler 1Test
spoiler Spoiler 2 Test
Spoiler 3Test
::: :::
[โ€“] [email protected] 3 points 1 month ago* (last edited 1 month ago) (1 children)

Thanks. I'll take a look.

Not an issue I would have thought to check since you should always close the tags you open lol ๐Ÿคท๐Ÿปโ€โ™‚๏ธ

[โ€“] [email protected] 2 points 1 month ago* (last edited 1 month ago) (1 children)

Right??? I wonder if that is even intentional. That also makes it so you cannot have two child spoilers nested at the same level within the same parent spoiler. Something like this should work, but noooooo, the end tags just don't work like you'd expect:

Spoiler 1Test
spoiler Spoiler 2a Test :::
Spoiler 2bTest
:::

Spoiler 1Test
spoiler Spoiler 2a Test :::
Spoiler 2bTest
:::

EDIT: Tesseract also adds an extra newline above each start tag in the code block above. In the actual comment source, there are no blank lines in the code block.

[โ€“] [email protected] 1 points 1 month ago* (last edited 1 month ago)

The newline is actually intentional. I use a different markdown renderer, and it needs it apparently; otherwise, it doesn't detect the closing tag. The Photon dev recommended another markdown library that works well with Svelte (which is why I switched from markdown-it), but I haven't had a chance to look into integrating it.