-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update explainer with button behaviors #1125
base: main
Are you sure you want to change the base?
Conversation
Also remove the split button section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to say anything about, the button needs to be the first child element of the select and no other buttons in the select participate this way?
Is this a requirement? |
having the button part being actually inert won't cause any issues in calculating the value of the select, will it? as we had previously resolved that if someone were to do:
that the value for the select would be returned as "foo bar" instead of the option's "bar baz" text |
It shouldn't. But we can prototype. I'm sure I can work around any issues.
…On Mon, Nov 11, 2024, 10:01 AM scottaohara ***@***.***> wrote:
having the button part being actually inert won't cause any issues in
calculating the value of the select, will it?
as we had previously resolved that if someone were to do:
<select>
<button> foo <selectedcontent>bar <span class="hide">baz</span></selectedcontent></button>
<option selected>bar <span class="hide">baz</span></option>
</select>
<style>
selectedcontent .hide { display: none }
</style>
that the value for the select would be returned as "foo bar" instead of
the option's "bar baz" text
—
Reply to this email directly, view it on GitHub
<#1125 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKQAZSE7P2TB5QHTUFBOIL2ADBFZAVCNFSM6AAAAABROIBNOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGM4DKMBYHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Not sure actually. But it feels to me like it would lead to some nice
predictability.
…On Fri, Nov 8, 2024, 5:04 PM Mason Freed ***@***.***> wrote:
Do we need to say anything about, the button needs to be the first child
element of the select and no other buttons in the select participate this
way?
Is this a requirement?
—
Reply to this email directly, view it on GitHub
<#1125 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKQAZVWETB3MTUGJTUXDJLZ7UYOLAVCNFSM6AAAAABROIBNOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVHAZDANBTGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Also remove the split button section.