it's a well known thing in react (preact does it well https://preactjs.com/guide/v10/differences-to-react/#use-oninput-instead-of-onchange https://preactjs.com/

it's a well known thing in react (preact does it well https://preactjs.com/guide/v10/differences-to-react/#use-oninput-instead-of-onchange https://preactjs.com/guide/v10/differences-to-react/#use-oni...), and probaly a design mistake on their side (now too late to change), I can't think of other cases like that