- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 16 Apr 2019 21:30:22 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 17 April 2019 04:30:45 UTC
rniwa commented on this pull request.
> @@ -483,10 +483,10 @@ empty list.
{{TouchEvent}} interface and related interfaces. [[TOUCH-EVENTS]]
<p>An <a>event</a> has an associated <dfn export for=Event>path</dfn>. A <a for=Event>path</a> is a
-<a for=/>list</a> of <a for=/>structs</a>. Each <a for=/>struct</a> consists of an
-<dfn for=Event/path>item</dfn> (an {{EventTarget}} object), an
-<dfn for=Event/path>item-in-shadow-tree</dfn> (a boolean), a <dfn for=Event/path>target</dfn> (a
-<a>potential event target</a>), a
+<a for=/>list</a> of <a for=/>structs</a>. Each <a for=/>struct</a> consists of a
+<dfn for=Event/path>current target</dfn> (an {{EventTarget}} object), a
+<dfn for=Event/path>current-target-in-shadow-tree</dfn> (a boolean), a
+<dfn for=Event/path>target</dfn> (a <a>potential event target</a>), a
Hm... maybe shadow-adjusted originating target? I think the key here is convey the semantics that the event looks as though it originated from that node in scripts.
Or we could call it *shadow adjusted target* or *visible originating target*. Or maybe even *embarkment target* or *source target*?
--
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/753#discussion_r276075395
Received on Wednesday, 17 April 2019 04:30:45 UTC