Re: [w3c/uievents] Add .pseudoTarget property to selected event types (PR #413)

@josepharhar 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 have a chromium change to do retargeting with WPTs but I'm still not sure whether pseudoTarget should always be null after event dispatch. Should we return the pseudoTarget when the event is dispatched in light dom and null when its dispatched in shadowdom, or should it always be null? https://chromium-review.googlesource.com/c/chromium/src/+/8008270

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/pull/413#discussion_r3500425009
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents/pull/413/review/4602360509@github.com>