- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 09 Oct 2023 23:37:05 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 10 October 2023 06:37:11 UTC
@LeaVerou the way custom elements handle this is very specific though to avoid crossing the C++/JS bridge too many times. Having to run a lot of script while building up an event's path isn't acceptable.
It does seem like there are a number of use cases where you want to be able to manipulate the parent post-construction. That argues for some kind of revealing constructor pattern or something similar to `ElementInternals`, e.g.,
```webidl
[Exposed=*]
interface EventTargetInternals {
attribute EventTarget parent;
};
callback EventTargetCallback = undefined (EventTargetInternals internals);
partial interface EventTarget {
constructor(optional EventTargetCallback cb);
};
```
--
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/583#issuecomment-1754494834
You are receiving this because you are subscribed to this thread.
Message ID: <whatwg/dom/issues/583/1754494834@github.com>
Received on Tuesday, 10 October 2023 06:37:11 UTC