Let’s try
[details open]
This should be visible
[/details]
This should be visible
And
<details open>
This should be visible
</details>
I don’t know when this broke, because I don’t use it every day. But [details open] worked earlier. I use open every now and then when sharing AI conversations.
Hmm unfortunately this looks like a regression from quite a while ago.
This won’t be an urgent fix for us so adding a pr-welcome for now.
Fair enough.
It is rarely used, I reckon. And I can bypass it using <details> and <summary>. I lose that cool AI-tag then, but perhaps I’ll survive without it 
Hey. I have always used details like this
[details="open"]
This should be visible
[/details]
This should be visible
I wasn’t aware you could also use
<details open>
This should be visible
</details>
Will try with the =
<details=“open”>
This should be visible
Doesn’t work as above
<details="open">
This should be visible
</details>
Only seems to work as per your last example.
Kind of cool though as the <> see s to default to open. Always learning new things)routes in discourse.
Damn. I can’t use the <details open> trick, because I have a totally wonderful design of Different look for details-block - #2 by Don in use.
Well, I must wait until someone who understands how things work has time to solve this. Not a deal breaker, though.
That is pretty sweet! Thanks for highlighting Don’s awesome component!
That will do it:
I was waiting for laundromat 
That comment made my day
Thanks!
I see the topic was opened. It was closed earlier. Answers my question to Jag. Thanks
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
