- From: Anne van Kesteren <notifications@github.com>
- Date: Thu, 10 Sep 2020 00:40:12 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 10 September 2020 07:40:25 UTC
@annevk commented on this pull request. > -<a>event listeners</a> whose -<a for="event listener">capture</a> variable is set to true are invoked, in -<a>tree order</a>. Second, object's own -<a>event listeners</a> are invoked. And -finally, and only if <a>event</a>'s -{{Event/bubbles}} attribute value is true, -object's <a>ancestor</a> -<a>event listeners</a> are invoked again, -but now in reverse <a>tree order</a>. - -Let's look at an example of how <a>events</a> work in a <a>tree</a>: - -<pre class='lang-markup'> +<p>When an <a>event</a> is <a>dispatched</a> to an object that <a>participates</a> in a <a>tree</a> +(e.g., an <a for=/>element</a>), it can reach <a>event listeners</a> on that object's +<a>ancestors</a> too. Effectively, all the object's <a>inclusive ancestor</a> <a>event listeners</a> It's an approximation as shadow trees and the `Window` object make it more involved than this. Not sure how to capture that succinctly though. -- 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/pull/890#discussion_r486129977
Received on Thursday, 10 September 2020 07:40:25 UTC