Re: [whatwg/dom] Do not dispatch a trusted event when target and reletedTarget are identical (#336) from Darien Maillet Valentine on 2023-03-14 (public-webapps-github@w3.org from March 2023)

From: Darien Maillet Valentine <notifications@github.com>
Date: Mon, 13 Mar 2023 19:03:48 -0700
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/pull/336/c1467230856@github.com>

> In theory, it doesn't matter how I set relatedTarget, the condition shouldn't allow callback functions to be called. But for some reason it doesn't match.

The internally associated “relatedTarget” (not sure why it’s camel cased in the spec, I thought the norm for this was using regular spaces) isn’t the `relatedTarget` attribute of `UIEvent`. The UIEvent attribute (→ ES accessor property) exposes it for those UIEvents specifically, but it exists for all events as private state. Setting a data property with the same name doesn’t do anything.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/pull/336#issuecomment-1467230856
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/pull/336/c1467230856@github.com>

Received on Tuesday, 14 March 2023 02:04:01 UTC