-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add <selectedcontent>
element
#528
base: gh-pages
Are you sure you want to change the base?
Conversation
</td> | ||
<td> | ||
<p> | ||
<strong class="nosupport"><a>No `role`</a> or `aria-*` attributes</strong> |
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.
would generally agree with this... just again noting to make sure this is thought about regarding how this gets mapped in html aam and if that could result in anything useful being allowed here.
Noting here that there will need to be an entry for a |
Where should I put this? |
<selectedoption>
element<selectedcontent>
element
oh no worries @josepharhar that was a note for me, not so much for you. if you did want to take it on, we'd need a new button as a child of a select entry in the table - using a similar ID like I'm setting up over in html aam but really, don't worry about it. i was planning on working on finishing this PR once the HTML/HTML AAM PRs were a bit closer to done. |
The
<selectedoption>
element is part of the customizable select feature and is being added to HTML here.It is already implemented in chromium and will be shipped when customizable
<select>
is shipped.labels: needs implementation commitment, needs changelog entry
Closes #0000
test case
Preview | Diff