Calculator: keyboard input sometimes broken when multiple instances open

[ZenMasta]

Describe the bug
If you have more than one instance of Calculator open, which ever instance is not the "original" will lose certain keyboard functions.

For example pressing escape to clear, backspace to backspace and enter to sum. These keyboard keys no longer work on the second instance. I cannot reproduce this 100% of the time. But every time I have encountered this problem, it was when multiple instances were opened. And

Steps To Reproduce

1. Open calculator
2. Hold shift and lose focus of the window (easiest way to do this is just to hold shift and left click somewhere outside the window)
3. Regain focus of the window
4. Press keys such as enter backspace escape p l x y and probably more

Expected behavior
Keyboard input should be observed no matter how many instances of calculator are open.

Device and Application Information

• OS Build: 10 0 17134 0"
• Architecture: X64
• Application Version: 10.1903.21.0
• Region: en-US
• Dev Version Installed: False

Note: A team member edited this comment to clarify steps to reproduce.

[MicrosoftIssueBot]

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

[grochocki]

Thanks for filing this! I cannot reproduce the problem myself, but will keep this open to see if we can collectively get to the bottom of why you might be seeing this behavior. I am on a newer app and OS version, so it could be the case that this newer combination doesn't have the same bug.

My machine info:

• OS Build: 10.0.18883.0
• Architecture: X64
• Application Version: 10.1905.3.0
• Region: en-US
• Dev Version Installed: True

[Timon23]

I can reproduce it on my machine consistently.

I think it has to do with the shift key.
If you hold shift and lose focus of the window and go back it'll still think the shift key is held.
If you press shift again it'll work like expected.

Oddly enough after that it doesn't do it again.

At first holding shift blocks all those keys from executing.
After pressing shift to make it work again, shift doesn't block the keys anymore.

Steps To Reproduce

1. Open calculator
2. Hold shift and lose focus of the window (easiest way to do this is just to hold shift and left click somewhere outside the window)
3. Regain focus of the window
4. Press enter/backspace/escape/p/l/x/y and probably more

Expected behavior

Those keys should still work.

• OS Build: 10.0.17763.503
• Architecture: X64
• Application Version: 10.1903.21.0
• Region: de-DE
• Dev Version Installed: False

[ZhaoMJ]

I can reproduce it on my own machine as well.

My machine info:

• OS Build: 10.0.18362.86
• Architecture: X64
• Application Version: 10.1903.21.0
• Region: en-US with zh-CN installed
• Dev Version Installed: False

[ZenMasta]

So I can reproduce this on my PC at home.

And incidentally. Maybe I was mistaken when I was trying to document this at work. But at least for me, on my home pc, it's actually the first instance that loses certain keyboard functions. Although I am still unable to reproduce it 100% of the time. Perhaps it's just inconsistent.

But as Timon23 pointed out. I agree that it is related to using shift. Although it doesn't have to be because I used shift+click to open another instance of the app.

I discovered if you just click the calculator icon from the start menu, that by itself will open another instance. So then I experimented just by pressing shift losing focus and then going back to a calc instance, that one of them loses the specific keyboard inputs.

After a few more experiments. I think it only happens on the specific instance that was most recently active before.

I've gone ahead and recorded this in action https://youtu.be/aCf8SCNggss

OS Build: 10.0.18362.0 (as reported by powershell), but winver shows 18362.113
Architecture: X64
Application Version: 10.1903.21.0
Region: en-US
Dev Version Installed: False

[grochocki]

I can reliably reproduce this issue now with steps @Timon23 added. Thank you!

After a few more experiments. I think it only happens on the specific instance that was most recently active before.

I think this is the case. I can get it to repro in the last active window (and even both, if I do the repro steps for each instance separately).

[HowardWolosky]

Interestingly enough, it stops repro'ing if you hit + or * on the keyboard. Once you've done that, Enter starts to work again. Oddly, if instead you tried hitting - or / on the keyboard, the repro continues. Odder still, the "fix" only works if using + or * from the keyboard, not the keypad.