-
Notifications
You must be signed in to change notification settings - Fork 378
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 custom element default focusability proposal #834
Conversation
Are you proposing this as an agenda item for #826? |
Yeah I think it'd be nice to talk about this in the TPAC session! |
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.
LGTM with nits
The proposed API above uses a CSS selectors to represent the built-in elements, but we’ve also considered some variants: | ||
|
||
- Using “tagname + one attribute name + attribute’s value” combination, | ||
e.g. `elementInternals.matchFocusBehaviorOf = {"input", "type," "button"}` |
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 isn't valid JS syntax. Maybe matchFocusBehaviorOf("input", "type", "button")
or three separate attributes or something like that.
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.
Oops, changed. Thanks!
Could you add a comment in the issue? |
Co-Authored-By: Domenic Denicola <[email protected]>
Mostly a summary of discussions in #762.
The proposed API uses CSS-selector like syntax, but other shapes for the API are also listed in the "alternatives considered" part.
cc @domenic @tkent-google @rniwa @alice @annevk from the thread