Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201) from Anne van Kesteren on 2023-05-22 (public-webapps-github@w3.org from May 2023)

From: Anne van Kesteren <notifications@github.com>
Date: Mon, 22 May 2023 05:43:41 -0700
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/issues/1201/1557153770@github.com>

Fair, might be good to wait a bit for others to chime in. In my mind this was always the event's path, but we didn't call it that because it had to be partially obscured in the presence of shadow trees. So I would expect Firefox's behavior and if we ever added the ability for userland `EventTarget` to hook into "get the parent" that would be reflected here as well.

(These days we would probably not add an API that so casually reveals open shadow trees however.)

cc @smaug---- 

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

Message ID: <whatwg/dom/issues/1201/1557153770@github.com>

Received on Monday, 22 May 2023 12:43:47 UTC