Hi Mike: Thanks for the reply. Here’s the result from the keypress tester:
keydown e.keyCode=0 e.which=0 e.keyIdentifier=Unidentified e.key=UIKeyInputEscape e.altKey=false e.ctrlKey=false e.altGraphKey=false e.metaKey=false e.shiftKey=false e.location=0 e.keyLocation=0 keypress e.keyCode=85 e.which=85 e.keyIdentifier= e.key=UIKeyInputEscape e.altKey=false e.ctrlKey=false e.altGraphKey=false e.metaKey=false e.shiftKey=false e.location=0 e.keyLocation=0 keyup e.keyCode=0 e.which=0 e.keyIdentifier=Unidentified e.key=UIKeyInputEscape e.altKey=false So… looks kind of funny. The keycode reported is ’85’ which is the U character, but the key that’s reported is ‘UIKeyInputEscape’, which is clearly not ‘U’, and also not ESC (27). Googling ‘UIKeyInputEscape’ suggests that this is UIKit’s name for the escape key, but the keycode is wrong. Does Guacamole have some idea of an editable keymap? And if it did, would it be looking at the ‘key’ value or the ‘keycode’ value? Cheers, Greg Trasuk > On Nov 24, 2017, at 1:58 AM, Mike Jumper <mike.jum...@guac-dev.org> wrote: > > On Thu, Nov 23, 2017 at 10:56 PM, Mike Jumper <mike.jum...@guac-dev.org> > wrote: >> On Thu, Nov 23, 2017 at 1:46 PM, Greg Trasuk <tras...@stratuscom.com> wrote: >>> Hi all: >>> >>> I’m trying to use Guacamole with an iOS device (I’ve tried both iPad and >>> iPhone devices) with an IOGear GKB632B keyboard >>> (https://www.iogear.com/product/GKB632B/) >>> >>> The problem is that Guac doesn’t seem to understand the keyboard mapping, >>> particularly for the escape key (and I would guess other keys as well, but >>> all I’m trying to do is use ‘vi’). On this keyboard When used through >>> Safari on the iOS devices, the escape key generates a ‘U’ character. It >>> works when connected to a MacBook. >>> >>> Any ideas? >>> >> >> It's possible that iOS Safari is not actually generating JavaScript >> key events for the keyboard at all. I've seen this in the past with >> bluetooth keyboards on iOS. >> >> What do you see when you try using that keyboard on iOS with the >> generic JavaScript key event tester at >> http://guacamole.apache.org/pub/tests/key-event-test.html ? (Please >> test both with and without the input field focused). >> > > Errr ... never mind on not generating events - clearly, if a key is > being typed as a result, even if incorrect, some sort of event is > making it through. > > The JavaScript key event tester may reveal what's actually inside > those events, and why Guacamole thinks you're typing a "U". > > - Mike
