Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)

> Re, Events: CustomElementRegistry is not currently an EventTarget, though it could be. But I think events are less ergonomic because you can't specify what tag names you care about, so you have to filter in the event handlers.

Why would `CustomElementRegistry` need to be an event target? `HTMLUnknownElements` could emit events when they're connected, which could bubble. This way one could listen for, say, an `unknown-element` event on the document, and be able to get the `target` to reason about what to do about it. This would be complementary to CE APIs.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/782#issuecomment-1525639111
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/782/1525639111@github.com>

Received on Thursday, 27 April 2023 12:49:41 UTC