Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Cannot type 3 & 9 on the number row #129

Closed
kanokkorn opened this issue Nov 2, 2019 · 14 comments
Closed

Cannot type 3 & 9 on the number row #129

kanokkorn opened this issue Nov 2, 2019 · 14 comments
Labels
type: imperfection Something isn't working
Milestone

Comments

@kanokkorn
Copy link

kanokkorn commented Nov 2, 2019

Describe the bug
Cannot type 3 & 9 on the number row

To Reproduce
Steps to reproduce the behavior:

  1. press 3 or 9 on the number row

Expected behavior
expected key to be working properly

Screenshots
Type with on-screen keyboard

Desktop (please complete the following information):

  • OS: Windows 10 Pro
  • Version: 10.0.18362 Build 18362

Update

  • happened with number 3 too
@kanokkorn kanokkorn added the type: imperfection Something isn't working label Nov 2, 2019
@kanokkorn kanokkorn changed the title Cannot type parentheses on number 9 key Cannot type 3 & 9 on the number row Nov 2, 2019
@satiowadahc
Copy link

Are you using a US keyboard layout? If you do a command line systeminfo what's the output of System locale and Input locale?

@kanokkorn
Copy link
Author

Are you using a US keyboard layout? If you do a command line systeminfo what's the output of System locale and Input locale?

Yes, I'm using a US keyboard layout. Here is the output.

System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)

@OriginalAdric
Copy link

Trying to clarify the issue: The 3 and 9 keys are being handled as PgDn and PgUp, respectively, both on the number row and numpad. The numpad behavior occurs regardless of Numlock status. The only difference in behavior I've observed is that Shift+3 and Shift+9 also select any text the cursor passes while Shift+Numpad3 and Shift+Numpad9 do not.

This occurs on my desktop Windows PC with full keyboard, both with physical keyboard and on-screen keyboard.
This does not occur on my Surface Pro 3 with magnetic keyboard, either with physical or on-screen keyboards.

@Sheel-1609
Copy link

Hi, i have the same problem on my HP laptop. @OriginalAdric is right this 9 and 3 are acting as page up and page down respectively. I have tried this with both US and UK keyboard styles the same problem persists. same with the numpad numbers. This problem also exists with an external keyboard.

@flaviosg
Copy link

I have the same problem. I'm using US English International Keyboad layout, with Windows 10.
"9" key acts as PgUp and "3" key acts as PgDw.
I can only type "3" using ALT+51 and "9" using ALT+57

@Ometeo
Copy link

Ometeo commented Nov 21, 2019

Hi, I have the same problem with the French Keyboard layout, if it helps.
OS : Windows 10
Keyboard : Razer Anansi

@svenefftinge svenefftinge added this to the v0.0.4 milestone Nov 28, 2019
@jankeromnes
Copy link
Member

I wasn't able to reproduce this bug in Arduino Pro v0.0.3, on both Windows 7 and Mac OS:

  • inputting 3s and 9s always worked fine (from on-screen keyboard, physical keyboard, numrow and numpad)
  • the only way I could get a 3 or 9 to act as different keys was by turning off NumLock and using the numpad (numrow and on-screen keyboard still input 3s and 9s fine without NumLock)

Maybe this bug is specific to Windows 10?

@kittaakos
Copy link
Contributor

I could reproduce it neither on Windows 10 nor macOS; worked as expected with EN_US layout. I am going to try it again with a real Windows machine with a numpad.

@kittaakos
Copy link
Contributor

It also works on Windows 7 with numpad. I have tried it with the physical and the on-screen keyboard too.

@spoenemann
Copy link

spoenemann commented Jan 10, 2020

I cannot reproduce this on my Windows 10 machine.

@kanokkorn @OriginalAdric @Sheel-1609 @flaviosg @Ometeo
Could you help analyzing the problem?

  1. https://w3c.github.io/uievents/tools/key-event-viewer.html (preferably with Chrome)
  2. Enter 39 in the input field
  3. Make a screenshot of the web page and attach here (if it's the same output as already posted by others, there's no need to post it again)

@kanokkorn
Copy link
Author

I think I can reproduce this by

  1. changing the language to non-US layout
  2. type with a non-US layout
  3. switch back to US layout

Test on Windows 10 and Ubuntu 18.04 TLS but can't reproduce this bug on Ubuntu. I will test again on a different machine.

@spoenemann
Copy link

Finally I could reproduce this. Cause: the mapping returned by native-keymap contains an entry

    "Numpad3": {
        "vkey": "VK_NEXT"
    }

VK_NEXT is the Windows virtual key code for PageDown; this leads to a keybinding mapping where PageDown is replaced with 3.

@spoenemann
Copy link

This must be fixed in Theia:
eclipse-theia/theia#6872

@spoenemann
Copy link

Should be ok with the next update.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: imperfection Something isn't working
Projects
None yet
Development

No branches or pull requests

10 participants