-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Correct WAI-ARIA integration for custom elements #8974
Conversation
This requires corresponding changes in https://w3c.github.io/core-aam/ as discussed in w3c/core-aam#152.
If #8962 lands first this will need changes to account for that and vice versa. |
@@ -14249,6 +14253,19 @@ interface <dfn interface>DOMStringMap</dfn> { | |||
<li><p>If <var>map</var>[<var>stateOrProperty</var>] <span data-x="map exists">exists</span>, | |||
then return it.</p></li> | |||
|
|||
<li> |
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.
I think we should prioritize this higher than the internal content attribute map. Otherwise, for the element-valued properties you'll get the empty string.
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.
This requires corresponding changes in https://w3c.github.io/core-aam/ as discussed in w3c/core-aam#152.
@scottaohara @alice @spectranaut I think WAI-ARIA will want to define a similar contract around ARIA properties. Namely that for each of them you get a string, element, list of elements, or their default value.
/common-dom-interfaces.html ( diff )
/custom-elements.html ( diff )
/dom.html ( diff )