- From: Justin Fagnani <notifications@github.com>
- Date: Fri, 11 Oct 2019 11:45:19 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 11 October 2019 18:45:22 UTC
@dvoytenko absolutely, especially in combination with `::part()`. A custom element may very well want to make public a part that itself has state, and the part may not be a custom element itself. The natural way to do this would be to have the custom element set the state on the part. I would like that feature, and it's been discussed, but I would rather have basic custom state support sooner. The workaround is to make a custom element just for to have custom state settable from the outside, maybe a `<div-with-state>` element. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/738#issuecomment-541180253
Received on Friday, 11 October 2019 18:45:22 UTC