- From: Hayato Ito <notifications@github.com>
- Date: Mon, 10 Sep 2018 07:57:05 +0000 (UTC)
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 10 September 2018 07:57:28 UTC
If we all agree on the new behavior, and the spec is updated, I'll try to align the Blink's behavior to the new one on Chrome Canary. Given it would be really difficult for us to predict what would be broken with this change, it would be worth trying this change on Chrome Canary as well as WebKit, and seeing what would be broken in wild. If someone knows any better way to evaluate the impact of this change, please let us know that. I'll add chromestatus entry for this change so that web developers can be noticed with this change. > It's a lot more likely that some event listeners on different elements are relying on event listeners on another element getting events before/after them by stopping propagation, etc... Yes, that could be more likely. -- 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/685#issuecomment-419822016
Received on Monday, 10 September 2018 07:57:28 UTC