- From: Emilio Cobos Álvarez <notifications@github.com>
- Date: Tue, 10 Nov 2020 14:10:07 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 10 November 2020 22:10:19 UTC
> So this is essentially a feature the web component frameworks like lit-html need to support /I need to implement myself? I suspect so, it doesn't seem hard to implement some sort of base class that does this. The firefox UI uses [similar patterns](https://searchfox.org/mozilla-central/rev/02cb78667e87ccc42fea5edc6f3f2dd2edd6ecd5/toolkit/content/customElements.js#260) for "inheriting" attributes and such. Making this "magic" is probably a breaking change (though I guess there could be some sort of opt-in at the component registration level...), plus you'd probably also want a `get onmycustomevent()` / `set onmycustomevent()` etc, right? Those are I suspect even more tricky to implement transparently / magically, they need to live somewhere in the proto chain of the element, so making that happen without anything in the class declaration that you use for registration seems a bit hard. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/908#issuecomment-724997284
Received on Tuesday, 10 November 2020 22:10:19 UTC