Hmm, maybe the way I linked in the parent comment, which github uses, would be better because it is more generic? I would like to use it in non-code use cases. So the collapsed content could...
Hmm, maybe the way I linked in the parent comment, which github uses, would be better because it is more generic? I would like to use it in non-code use cases.
So the collapsed content could contain code-formatted text, or any other existing style.
IIRC Tildes uses the Github Flavored Markdown spec, so supporting <details> and <summary> may be as simple as enabling them in the parser. I made an issue to investigate:...
IIRC Tildes uses the Github Flavored Markdown spec, so supporting <details> and <summary> may be as simple as enabling them in the parser. I made an issue to investigate: https://gitlab.com/tildes/tildes/issues/150
Sure would be nice if that worked. Like this: https://github.com/dear-github/dear-github/issues/166#issuecomment-236342209
edit: spelling
It probably will at some point: https://gitlab.com/tildes/tildes/issues/137
Hmm, maybe the way I linked in the parent comment, which github uses, would be better because it is more generic? I would like to use it in non-code use cases.
So the collapsed content could contain code-formatted text, or any other existing style.
edit: phrasing
IIRC Tildes uses the Github Flavored Markdown spec, so supporting <details> and <summary> may be as simple as enabling them in the parser. I made an issue to investigate:
https://gitlab.com/tildes/tildes/issues/150
Thank you!
Test of using an html tag called details, only one time. Tildes seems to auto-add the closing </blah> tag.
Does it close any random tag text?
<random>Yup, it does.