13:01
<smaug>
Hmm, https://html.spec.whatwg.org/#activation-triggering-input-event doesn't make sense
13:01
<smaug>
mousedown and pointerdown both there, so each of them could trigger something
13:02
<smaug>
or is there somewhere some limitation about that situation
16:41
<mikedidomizio>

Hey everyone, new to Matrix so hopefully this is the right place to ask.

What was the reasoning making the <details> element firing the ontoggle event when it renders with open attribute being present?

We use Next.js/React at work, and I think most devs expect that most events are triggered by something done by the user, like onchange, onsubmit, onclick.
So it isn't far-fetched to assume a dev would believe ontoggle would be triggered when the <details> is opened/closed and not necessarily because it has mounted/rendered open.

Maybe I'm misreading this GitHub issue but if I'm reading it correctly, it does sound like there were some concerns about that as well - https://github.com/whatwg/html/issues/4500