ID:1675757
 
Resolved
The default input control grabbed focus for key events that had a macro with fewer modifier keys, when the correct behavior was to fire the macro and not grab focus.
BYOND Version:507
Operating System:Windows 8 Pro 64-bit
Web Browser:Chrome 37.0.2062.103
Applies to:Webclient
Status: Resolved (507.1256)

This issue has been resolved.
For games that use "WASD to move" and "Hold Shift to run", pressing any key while shift is down will give focus to the input control.

e.g. while running, press any movement key to give focus to the input, press any other movement key to fill the input with letters.

It happens with arrow keys, too, but it's somewhat nicer because arrow keys aren't sent to the input while shift is down. (they are when ctrl is down, but that's intentional)

I think it was fixed before that pressing shift would cause input focus. This is different, but happens in similar contexts.
If you have a demo that doesn't take forever to start up it would be a big help. I've mostly seen this WASD stuff in Yut Put's games and those are nightmares to test.
Thanks. That project ended up being a big help for debugging.
Lummox JR resolved issue with message:
The default input control grabbed focus for key events that had a macro with fewer modifier keys, when the correct behavior was to fire the macro and not grab focus.