Thanks Nick. On Fri, Mar 30, 2018 at 2:19 AM, Nick Couchman <vn...@apache.org> wrote:
> On Thu, Mar 29, 2018 at 2:46 PM, Mike Jumper <mike.jum...@guac-dev.org> > wrote: > >> On Thu, Mar 29, 2018, 09:41 Amarjeet Singh <amarjee...@gmail.com> wrote: >> >>> Hi Team, >>> >>> While I am pressing Super key ( as if user is clicking start menu icon ) >>> in RDP. Chrome recognize it as *Meta key* and there is no scan code of >>> Meta key in base.keymap. >>> >> >> If Chrome is recognizing key X as key Y, that would be a bug in Chrome. >> The "Super" key should not be recognized by the browser as "Meta". >> >> > It does seem to be Chrome-specific - the keycode is exactly the same, but > Chrome seems to recognize the key as a Meta key. I'm not sure if this is a > bug or by choice. Here's the output from your test page in Chrome: > > keydowne.keyCode=91e.which=91e.keyIdentifier=undefinede.key=Meta > e.altKey=falsee.ctrlKey=falsee.altGraphKey=undefinede.metaKey=false > e.shiftKey=falsee.location=1e.keyLocation=undefined > keyupe.keyCode=91e.which=91e.keyIdentifier=undefinede.key=Meta > e.altKey=falsee.ctrlKey=falsee.altGraphKey=undefinede.metaKey=true > e.shiftKey=falsee.location=1e.keyLocation=undefined > > and from Firefox: > > keydown e.keyCode=91 e.which=91 e.keyIdentifier=undefined e.key=OS > e.altKey=false e.ctrlKey=false e.altGraphKey=undefined e.metaKey=false > e.shiftKey=false e.location=1 e.keyLocation=undefined > keyup e.keyCode=91 e.which=91 e.keyIdentifier=undefined e.key=OS > e.altKey=false e.ctrlKey=false e.altGraphKey=undefined e.metaKey=false > e.shiftKey=false e.location=1 e.keyLocation=undefined > > keyCode is 91 for both, but Chrome sets e.metaKey=true, Firefox does not. > > -Nick >
