Re: [WICG/webcomponents] Proposal: Custom attributes for all elements, enhancements for more complex use cases (Issue #1029)

Couple other points related to the basic design of the class:

1. I think the MVP lifecycle would include `ownerConnected/DisconnectedCallback` so that behavior can be triggered based on the element being "in use" in the DOM. Quick example: there's a data subscription attribute and the attribute needs to be able to disconnect from some system when the element is no longer used in the tree.
2. The one-to-one mapping between behavior enhancement and attribute name/value feels limiting/cumbersome. Contrived example: 
    * `<input has="happy sad bored" onhappy... onsad... onbored...>` v. 
    * `<input has="moods" onhappy... onsad... onbored...>`

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

Message ID: <WICG/webcomponents/issues/1029/1719996635@github.com>