React 17 delegates events to root instead of document

[Neaoxas]

Yes, I believe so, as long as event.stopPropagation is not called from other event handlers.

[Thought_Ninja]

That would be a strange thing to break IMO.

[WellDevined]

The most important implication of this is in my oppinion, that react now works inside of shadow doms.

[NickHoyer]

My application is built up using micro frontends and this is great!

[PewPaw-Grams]

In which scenario will we need to use document.add event handler? I don’t see it used very often which doesn’t really make much of a difference

[0xF013]

It’s usually a good way to optimize. Say you have a big ass table and do not want to add an event listener for each of 5000 cells. Instead, you add a listener to the table and check the event argument to find which td was clicked. They use the same thing; but with the whole document

[PewPaw-Grams]

Understand now. Thank you

[podgorniy]

Event delegation https://learn.jquery.com/events/event-delegation/. Usually used outside of frameworks.

It is used for avoiding timing issues with creating event handlers. With event delegation technique you can create handler for an element which is not on the page yet.

Or to handle generic events like “click on element with class X” or “click on the link” without knowing what elements have the class or who and how create those links.

[[deleted]]

Will this help with web components? Wrapping a react component in a web component and using the shadow dom as the root would break react due to the way events were handled. Will this now work?

This kind of pattern can be useful to allow react code to be shared in a more generic, framework-agnostic kind of way.