Xpra: Ticket #858: HTML 5 Client does not have NumLock sync

Tested with the following against a Fedora 21 r9329 trunk and 0.15.0 server:

In the Windows HTML5 viewer, I can hit the NumLock? button and it will work for one character, then it goes back to disabled. This is problematic as Windows will also toggle its NumLock? which will cause a desync of NumLock? - this was fixed in #312

In OSX, it is especially problematic as I can not enable NumLock? due to Apple keyboards, annoyingly, not having a NumLock? key, just a key marked 'clear' that apparently doesn't do anything.



Wed, 13 May 2015 02:14:51 GMT - Antoine Martin:

Some information that might be useful for fixing this:

Grepping the source code for num*lock will turn up quite a few hits.


Sun, 10 Apr 2016 06:07:21 GMT - Antoine Martin: owner, milestone changed

@maxmylyn: is this still a problem?


Tue, 12 Apr 2016 21:03:15 GMT - J. Max Mena: owner changed

As of r12379 I still do not have numlock. Hitting the NumLock? key has no effect (other than toggling it on my local machine)


Sat, 11 Jun 2016 17:00:25 GMT - Antoine Martin: owner changed

Done in r12797.

Important caveat: there is no way of knowing the current state of numlock in Javascript, so we manage it ourselves and toggle the value whenever we detect that the numlock key is pressed (and we only get those events if we have focus when they occur). So numlock can very easily start / go out of sync with the real keyboard state.


Mon, 13 Jun 2016 18:54:02 GMT - J. Max Mena: status changed; resolution set


So numlock can very easily start / go out of sync with the real keyboard state.


Noted. Quick and dirty workaround is to disconnect, toggle numlock (so it'll match with the server), then reconnect. I'm not sure if there's going to be an elegant fix since browsers are so sandboxed.

Closing.


Tue, 14 Jun 2016 09:43:14 GMT - Antoine Martin:

Quick and dirty workaround is to disconnect, toggle numlock


As per comment:4, you can do the same thing without disconnecting: just hit numlock whilst the xpra browser window is NOT receiving the key events (focus some other window or minimize the browser temporarily). That's a lot easier than re-connecting.


Tue, 12 Jul 2016 16:52:22 GMT - Antoine Martin: milestone changed

Milestone renamed


Sat, 23 Jan 2021 05:08:03 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/858