-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Use constants for keyCodes #1225
Comments
There's more of this in the unit tests now too... see the tests added by pull #1273, for example. |
Hi brackets people. Looking into fixing this issue- Jochen |
This is an easy fix but I wonder what the preferred place to define key constants would be. Do you want them in utils.Globals.js? |
I suppose a better place might be to put constants into a KeyEvent class in utils? Thanks for a quick comment. |
Joschen, Thanks for taking this on. I marked it as "Fix in Progress". Yes, I think a KeyEvent module in utils is perfect. |
Pull request pending. |
FBNC to |
Confirmed fixed by pull request #1583. |
Thursday Jul 12, 2012 at 20:31 GMT
Originally opened as adobe/brackets#1241
Most of Brackets code that looks at the keyCode member of an event compares it against the keyCode number. Brackets could would be more readable if keycode constants were used instead.
References regarding constants and keyCodes
http://www.javascripter.net/faq/keyeventconstantsfirefox.htm
http://stackoverflow.com/questions/1465374/javascript-event-keycode-constants
The text was updated successfully, but these errors were encountered: