[Platform-provided behaviors for CE] HTMLButtonBehavior with type attribute alternative#1356
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0d905bc to
92bcb54
Compare
dandclark
left a comment
dandclark
left a comment
There was a problem hiding this comment.
At a first pass through, I like this. Just left some general early thoughts on the design.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gregwhitworth
left a comment
gregwhitworth
left a comment
There was a problem hiding this comment.
Some general questions and primarily "nits". Thank you so much for your great work on this.
|
|
||
| ### Behavior categories and composition | ||
|
|
||
| Behaviors are organized into a set of categories. Categories are conceptual groupings the platform uses to decide which behaviors can coexist on one element. They are not classes exposed to authors; authors only ever reference the concrete behaviors (the leaves below). |
There was a problem hiding this comment.
@slightlyoff raised at one point in this conversation why we're having abstractions. I think it's worth outlining why we're doing this bucketing rather than giving them more granular access. I personally like this design as I think 99% of authors are going to just want all of the goodness out of the box and also not have to keep adding capabilities as we introduce them into the platform (this is coming from years of having to support something similar) but it's worth noting (maybe in appendix or similar) why we're not currently exploring this path. I'm interested in @dandclark and your thoughts as this may also open a can of worms.
There was a problem hiding this comment.
Agreed this deserves to be written down. The granular / à-la-carte path (expose focusability, activation, form participation, etc. as independent primitives) is the low-level-primitives direction in Alternative 7 of the main explainer. When I move this alternative into the main explainer, I will leave the comments pointing to the granular approach.
|
|
||
| Mapping a few native patterns onto categories helps validate the model: | ||
|
|
||
| | Native pattern | Behavior | Category | Notes | |
There was a problem hiding this comment.
I really think this table is a great example of the power this provides
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
anaskim
left a comment
anaskim
left a comment
There was a problem hiding this comment.
Thanks for the thorough feedback!
|
|
||
| ### Behavior categories and composition | ||
|
|
||
| Behaviors are organized into a set of categories. Categories are conceptual groupings the platform uses to decide which behaviors can coexist on one element. They are not classes exposed to authors; authors only ever reference the concrete behaviors (the leaves below). |
There was a problem hiding this comment.
Agreed this deserves to be written down. The granular / à-la-carte path (expose focusability, activation, form participation, etc. as independent primitives) is the low-level-primitives direction in Alternative 7 of the main explainer. When I move this alternative into the main explainer, I will leave the comments pointing to the granular approach.
gregwhitworth
left a comment
gregwhitworth
left a comment
There was a problem hiding this comment.
Thanks for the edits, I'm a go :)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
3 participants
Not for merging, just getting comments/feedback in-line.