search

jgosmann / Karabiner-Elements-Neo

Neo2 Layer 4/6 for macOS Sierra
The Unlicense
33 stars 5 forks source link

Mod3 + "o" (Neo) strange behavior in browsers #10

Closed neominik closed 7 years ago

neominik commented 7 years ago

Mod3 + "o" (Neo) doesn't insert "*" in text-fields on some web-pages but takes one a page back in history.

jgosmann commented 7 years ago

Can you specific about the browser in which you observed that and which mod3 key you were using?

neominik commented 7 years ago

I have tried Safari and Chrome both the same behaviour with both Mod3 keys (Caps-Lock and #). In text-fields on GitHub it strangely works as intended though. I'm using the keymap from the neo-layout page if that helps. Maybe I'm gonna try the one you provided.

jgosmann commented 7 years ago

Weird, I will see if I can reproduce it this evening (EST).

jgosmann commented 7 years ago

I can't seem to reproduce this. 😕

neominik commented 7 years ago

Hmm weird. Any way for me to debug this? The Karabiner Event-Viewer says the following when I press '*':

eventType:FlagsChanged    code:0x3d       name:right_option    flags:Opt                                misc:characters:    
eventType:KeyDown         code:0x5        name:g               flags:Opt                                misc:characters:    
eventType:KeyUp           code:0x5        name:g               flags:Opt                                misc:characters:    
eventType:FlagsChanged    code:0x3d       name:right_option    flags:                                   misc:characters:
jgosmann commented 7 years ago

That is the expected output. I think the problem is not with Karabiner, but the neo.keylayout.

neominik commented 7 years ago

I tried both neo.keylayout files now (with a reboot in between). they show the same behaviour. A specific page where * doesn't work is the code editor of codecademy.com. And I had the same problem with other online code editors.

tjanson commented 7 years ago

For the record, I can’t reproduce it either. Do you happen to have a keyboard with an actual numpad? Then you could test whether that has the same effect.

olbrichj commented 7 years ago

codecademy.com had those problems already with prior versions of karabiner. So I guess it's somewhere in their js-editor code which handles the mapping incorrectly

jgosmann commented 7 years ago

This seems to be nothing I can fix in Karabiner-Elements or neo2-layout-osx, it is probably as issue with the browser or JS application. I added a note to the known issues section of the readme about this.