Skip to content
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 custom element #180

Closed
scottaohara opened this issue Oct 4, 2019 · 0 comments · Fixed by #210
Closed

update custom element #180

scottaohara opened this issue Oct 4, 2019 · 0 comments · Fixed by #210

Comments

@scottaohara
Copy link
Member

Per: HTML issue 4658 and ARIA issue #984 it should be noted that a custom element may have no corresponding role (map to generic) or may have a role set by ElementInternals.

If the role is set in that way, and the custom element doesn't merely act as a container for child elements (light or shadow dom) with their own roles, then the listing for the custom element would need to indicate that it either maps to generic, OR the role set by ElementInternals.

In that case, the allowed state/properties/naming/etc. would be dependent on the role the element represents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant