- From: Caridy Patiño <notifications@github.com>
- Date: Tue, 26 Mar 2019 08:38:02 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 March 2019 15:38:24 UTC
As @pmdartus mentioned, the proposed changes look good, but I will like to get some clarification on why the current behavior was chosen in the first place. We discovered the issue described here while trying to test our synthetic shadow dom polyfill, and we were surprised by the behavior of all browsers. Why all composed events dispatched on the host elements in the event path regardless if the event bubbles or not? Seems counterintuitive, and leak internal implementation details of the component. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/742#issuecomment-476707927
Received on Tuesday, 26 March 2019 15:38:24 UTC