- From: smaug---- <notifications@github.com>
- Date: Thu, 02 Jul 2026 12:36:50 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents/pull/413/review/4620634769@github.com>
@smaug---- commented on this pull request.
> + <dd>
+ The [=pseudo-element=] that was the target of the interaction,
+ if any. When the event target is an element rather than a
+ [=pseudo-element=], this attribute is <code>null</code>.
+
+ Each {{UIEvent}} has an associated <dfn for="UIEvent">pseudoTargetOrigin</dfn>
+ internal slot (an {{Element}} or <code>null</code>), initialized to
+ <code>null</code>, and an associated <dfn for="UIEvent">pseudoTarget</dfn>
+ internal slot (a {{CSSPseudoElement}} or <code>null</code>), initialized to
+ <code>null</code>.
+
+ To get this attribute, run these steps:
+
+ 1. If the [=UIEvent/pseudoTargetOrigin=] internal slot is <code>null</code>, then return <code>null</code>.
+ 1. Let |currentTarget| be {{Event/currentTarget}}.
+ 1. If |currentTarget| is <code>null</code>, then return <code>null</code>.
I can live with either approach. One thing which makes this a bit trickier is that what if shadow DOM target is removed from Shadow DOM. That shouldn't affect whether the pseudoTarget is non-null after dispatch.
(Chrome has currently a bit related bugs to that when it comes to .relatedTarget handling - it ends up exposing shadow DOM stuff to light DOM).
So, I guess it would be easier to spec and implement if it was null always after dispatch.
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/pull/413#discussion_r3515664711
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/uievents/pull/413/review/4620634769@github.com>
Received on Thursday, 2 July 2026 19:36:54 UTC