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

@sorvell , so I think you are advocating allowing one behavior to "own" multiple (non-data?) attributes.  

Benefits I see:

1.  This would allow for the values associated with the behavior to be "spread out", not scrunched into a JSON object. 
2. It might be easier for the browser to "discover" the enhancements.
3. The names of the behaviors could be a single word.

Dangers:

1.  I think the message on "namespacing" the attributes becomes cloudier -- more than one "owned" name associated with a package, basically.  Maybe solvable with prefixes?
2. It still complicates simpler use cases (such as the log to console example), behaviors that only really expect to have one value throughout their lifespan.

Maybe that approach should be optional?
 

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

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