Add selectedcontent element and allowances for 'button' part of select#528
Add selectedcontent element and allowances for 'button' part of select#528patrickhlauke merged 14 commits intow3c:gh-pagesfrom
selectedcontent element and allowances for 'button' part of select#528Conversation
|
Noting here that there will need to be an entry for a |
Where should I put this? |
josepharhar
changed the title
<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. |
|
latest commit updates selectedcontent to align with recent HTML AAM changes. also added in the button as a child of select variant / expectations. |
scottaohara
changed the title
<selectedcontent> elementselectedcontent element and allowances for 'button' part of select
account for misuse of element - where the element will just be a generic element and thus is name prohibited, but any role/attributes can be used to modify/fix the errant element, as needed.
|
test case file created and added to OP - https://w3c.github.io/html-aria/tests/selectedcontent.html |
fixed to match other role markup: `<code>role=<a href="#index-aria-generic">generic</a></code>`
There was a problem hiding this comment.
Looks good to me (though note one question #528 (comment))
|
discussed with @scottaohara separately. we're ok with the current wording, as the specifics of what a "valid descendant of a |
3 participants
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.test case
Preview | Diff