Thanks for the information, everyone. I will try out a few different browser configurations.
-----Original Message----- From: Ryan Underwood [mailto:[email protected]] Sent: Monday, November 06, 2017 10:28 AM To: [email protected] Subject: RE: Capture keyboard input? ** WARNING: This mail is from an external source ** I forgot about the OS and Browser eating keys before you get them. With most browsers you can stop your browser from responding to those OR pop up a warning so it doesn't just happen without confirmation. Regards, -Ryan -----Original Message----- From: Mike Jumper [mailto:[email protected]] Sent: Monday, November 06, 2017 1:23 PM To: [email protected] Subject: Re: Capture keyboard input? On Tue, Oct 31, 2017 at 10:30 AM, Anthony Moon <[email protected]> wrote: > Hi all, > > Just wondering if Gauc has the ability to capture all keyboard input? > I can’t tell you how many times I’ve accidentally closed the whole tab > while typing (CTRL + W).. > Guacamole already attempts to capture absolutely all keyboard input. It's up to the OS and the browser to decide which key events to actually expose to JavaScript. Keyboard events for shortcuts reserved by the OS (Ctrl+Alt+Del, Alt+Tab, etc.) are typically eaten by the OS before they reach the browser, and keyboard events for shortcuts reserved by the browser (such as Ctrl+W) are typically eaten by the browser before they reach JavaScript. Some browsers, Chrome included, will allow bookmarks to be saved to the desktop or home screen, and give the webapps bookmarked in such a manner access to additional keystrokes. If the browser you're using has this feature, that may help things. Beyond that, it's a security feature of the browser that web applications cannot take full control of the keyboard, and there's nothing that can be done within JavaScript to alter this. As long as the key event actually happens within JavaScript, Guacamole will handle it and pass it along to the remote desktop. - Mike
