Re: [whatwg/dom] Event.composedPath() inconsistency between implementors. (Issue #1201)

> the name composedPath indicates it is for DOM Node

I’m unsure what about the name suggests that. While EventTargets constructed directly from user code never have a non-default [“get the parent” algorithm](https://dom.spec.whatwg.org/#get-the-parent) presently, IndexedDB interfaces extending EventTarget do — an IDBRequest’s parent is an IDBTransaction and an IDBTransaction’s parent is an IDBDatabase. The usual bubbling behavior applies.

As far as I can tell, `composedPath()` for e.g. an IDBRequest `success` event should reflect this, and in Firefox, it does:

![image](https://github.com/whatwg/dom/assets/6257356/98128739-5f75-4f8e-923b-fbd409c5c41b)

In Chromium presently, I get an empty array.

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

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