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

Add Meta Key mapping to xtscancodes.js #654

Closed
wants to merge 1 commit into from

Conversation

asadpanda
Copy link
Contributor

OSLeft/OSRight have been renamed to MetaLeft/MetaRight respectively.

This change will allow the Super/Windows key to be used under the qemu rfb extension under Chrome and updated browsers.

w3c/uievents-code#7
https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code

OSLeft/OSRight have been renamed to MetaLeft/MetaRight respectively.

This change will allow the Super/Windows key to be used under the qemu rfb extension under Chrome and updated browsers.

w3c/uievents-code#7
https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code
@samhed
Copy link
Member

samhed commented Sep 6, 2016

Do we need to keep the old names for some sort of compatibility?

@asadpanda
Copy link
Contributor Author

Yes, I would leave it for compatibility. https://bugzilla.mozilla.org/show_bug.cgi?id=1264150 is still open for firefox, even though they have updated their docs, it still sends the code "OSLeft" or "OSRight". That's actually how i discovered the bug in the first place, it worked fine under firefox.

@samhed
Copy link
Member

samhed commented Sep 7, 2016

Ok, could you add a comment to OSLeft and OSRight which explains the situation and I'll merge this

@DirectXMan12 DirectXMan12 added this to the v0.7.0 milestone Sep 16, 2016
@samhed samhed closed this in c7f2f11 Oct 19, 2016
@asadpanda asadpanda deleted the patch-1 branch November 2, 2016 20:00
@samhed samhed added the bug label May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants