Hey everyone,

I've been waiting to hear from mfreed and ntim regarding their thoughts on the <details> element, specifically how it works with ontoggle and the open attribute, but haven't seen any updates from them since my initial post.

At work we're potentially planning on modifying its behaviour (specifically we're considering preventing ontoggle from automatically firing if the open attribute is present) through a React component built on top of the <details> element.
After discussing this with my team, it became clear that the current behaviour isn't intuitive for most developers, and this leaves a chance of introducing more bugs into our code base (a bug is what started this all).
While I respect the WHATWG's decision on how they think things should work, if modifying behaviour prevents the likelihood of bugs in the codebase, and misunderstandings within my team, I’m willing to implement a change. That’s why we’re opting for a custom implementation to change how it works.

I'm still very interested in the reasoning behind the current design choices, and if this is something that should be revisited. A part of me wonders if I'm overthinking this, but I also worry how many devs in the future may misunderstand the behaviour of the <details> element, given how the ontoggle event handler works differently than how most (all?) other event handlers work.

I noticed you guys have a few meetings, I'm not sure if that's the correct place for you to discuss further, or for me to DM the folks mentioned above, or we continue to wait for them.

Thanks and let me know if there's anything I can do to help.