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.

Sign up for GitHub

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

Jump to bottom

[code] KeyboardEvent code spec should have featurephone section #39

Closed
garykac opened this issue Oct 7, 2015 · 1 comment
Closed

[code] KeyboardEvent code spec should have featurephone section #39

garykac opened this issue Oct 7, 2015 · 1 comment
Labels
important!

Comments

@garykac
Copy link
Member

garykac commented Oct 7, 2015

Copied from W3C Bugzilla: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27996

Masayuki Nakano 2015-02-11 01:53:20 UTC

D3E KeyboardEvent should cover the keys on featurephone because featurephone is still major device.

Therefore, D3E-code spec should have a section to explain which code values should be used if they can be distinguished, and also if they cannot be distinguished, which scancode for existing code values should be generated by the driver.

Our agreements are now, Numpad* for them but not yet discussed enough about the latter case.

Comment 1 Arthur Barstow 2015-03-21 15:11:50 UTC

Bulk move of all D3E bugs to the UI Events component.
@garykac
Copy link
Member Author

garykac commented Oct 21, 2015

This issue was moved to w3c/uievents-code#5

@garykac garykac mentioned this issue Oct 21, 2015
Closed
@garykac garykac closed this as completed Oct 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
important!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@garykac @travisleithead