> If a library author is on their 17th major version and is still deciding how core stuff like this works… Did you follow the link to understand what the chang

> If a library author is on their 17th major version and is still deciding how core stuff like this works… Did you follow the link to understand what the change is, and why they made it? [link] This isn’t some sweeping rewrite of an entire subsystem for the fourth time (I’m looking at you, Angular); it’s just changing React’s synthetic events to be attached to the react tree’s root node in the DOM instead of directly on the document. They have always been on the document until now. So there is no “still deciding” flip-floppery here, there was a single decision made to better support developers by making one low-impact change. How low-impact? > We’ve only had to change fewer than twenty components out of 100,000+ in the Facebook product code to work with these changes…[link] React is very good about semantic versioning. This change, small as it is, is a breaking change for a very small number of users. And that’s why it gets a new major version number. https://reactjs.org/blog/2020/10/20/react-v17.html#changes-to-event-delegation https://reactjs.org/blog/2020/10/20/react-v17.html#changes-t...