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

Tristate value type: the default value should be "undefined" #773

Closed
aristov opened this issue May 26, 2018 · 0 comments
Closed

Tristate value type: the default value should be "undefined" #773

aristov opened this issue May 26, 2018 · 0 comments
Milestone

Comments

@aristov
Copy link
Contributor

aristov commented May 26, 2018

The definition of tristate attribute value type states:

The default value for this value type is false unless otherwise specified.

There are only two states of this type: the "aria-checked" state and the "aria-pressed" state. Both of them have "undefined" as a default value.
The tristate type is like applicable (true/false/undefined) type, but with additional "mixed" value. Applicable type's default is "undefined".
So I suggest to change that confusing definition, which must be:

"The default value for this value type is undefined unless otherwise specified.

@aristov aristov changed the title Tristate: default value should be "undefined" Tristate value type: default value should be "undefined" May 26, 2018
aristov added a commit to aristov/aria that referenced this issue May 26, 2018
@aristov aristov changed the title Tristate value type: default value should be "undefined" Tristate value type: the default value should be "undefined" May 26, 2018
@jnurthen jnurthen added this to the ARIA 1.2 milestone Jun 14, 2018
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

No branches or pull requests

2 participants