- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 20 Jul 2016 00:34:41 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Message-ID: <whatwg/dom/pull/281/r71477836@github.com>
> @@ -639,10 +639,18 @@ dictionary EventInit {
> <p>An {{Event}} object is simply named an <dfn export id=concept-event>event</dfn>. It allows for
> signaling that something has occurred, e.g., that an image has completed downloading.</p>
>
> +<p>An <a>event</a> has an associated <dfn export for=Event>relatedTarget</dfn> (an
> +{{EventTarget}} object). Unless stated otherwise it is null.</p>
> +
> +<p>An <a>event</a> has an associated <dfn export>set the relatedTarget</dfn> algorithm,
> +which takes an {{EventTarget}} <var>relatedTarget</var>. Unless specified otherwise it does
> +nothing.</p>
So this algorithm exists because UI events need it and they need to do something different between normal UI events and Touch events?
Also, how does this work for synthetic events? I guess the event class defines it?
It's probably worth having a note here that points to the various implementations of this algorithm.
---
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/281/files/5a01009f0b85a5d88fef1accc95d65c63f89b829#r71477836
Received on Wednesday, 20 July 2016 07:35:33 UTC