Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029) from Keith Cirkel on 2024-11-04 (public-webapps-github@w3.org from November 2024)

From: Keith Cirkel <notifications@github.com>
Date: Mon, 04 Nov 2024 08:13:27 -0800
To: WICG/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <WICG/webcomponents/issues/1029/2455125948@github.com>

&gt; I&#39;m assuming that the dashes requirement is to avoid clashes with &#39;official&#39; attributes. This doesn&#39;t work, because with reflection, a `read-only` attribute still maps to a `readOnly` property, so you still have the namespace clash.

I agree and I&#39;m not sure custom attributes should be adding properties to elements. Custom Elements should be free to add the property which can look up the custom attribute node, and the custom attribute should be able to internalise its own reflection rules and expose them (perhaps via a `.value` getter or something) but I think the wiring should still be manual.

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

Message ID: &lt;WICG/webcomponents/issues/1029/2455125948@github.com&gt;

Received on Monday, 4 November 2024 16:13:31 UTC