We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From @garykac on October 7, 2015 0:26
The current spec doesn't define an 'Unspecified' value that can be used when the code value cannot be determined.
Having a separate value is important to be able to distinguish between 'not implemented' and 'implemented, but unable to determine code'.
Currently, we define 'Unspecified' for 'key', but don't have the equivalent text for 'code'.
Copied from original issue: w3c/uievents#20
The text was updated successfully, but these errors were encountered:
From @masayuki-nakano on October 7, 2015 0:51
There are 3 cases of empty code value under current spec:
It may be impossible to distinguish #2 and #3 if they causes same scancode or something, though. So, only #1 case could cause specific value?
Sorry, something went wrong.
s/Unspecified/Unidentified/
f2896af
No branches or pull requests
From @garykac on October 7, 2015 0:26
The current spec doesn't define an 'Unspecified' value that can be used when the code value cannot be determined.
Having a separate value is important to be able to distinguish between 'not implemented' and 'implemented, but unable to determine code'.
Currently, we define 'Unspecified' for 'key', but don't have the equivalent text for 'code'.
Copied from original issue: w3c/uievents#20
The text was updated successfully, but these errors were encountered: