Re: [WICG/webcomponents] 2023 TPAC F2F discussion? (Issue #1018)

Respectfully, I think that proposal falls short in a number of ways:

1.  For each behavior, the vendor needs to fully dictate what goes into the initial settings of the attribute (whether it be JSON or some other format).  Sharing one attribute for all behaviors would be too limiting.
2.  Having separate attributes conforms much more closely to proven solutions across multiple frameworks and across multiple decades of development.
3.  There's no explicit support for providing a public way for external components to interact with the behavior.  Not having that would make the proposal fall short of providing a true alternative to customized built-ins.
4.  It isn't a formal proposal.

There *is* a formal [proposal](https://github.com/WICG/webcomponents/issues/1000) that addresses all these concerns.  Any flaws that you see with it?

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

Message ID: <WICG/webcomponents/issues/1018/1658508431@github.com>