KeyDown event does not work with multiple keys pressed simultaneously

[alienghub]

Describe the bug

1. I press key A, A type keydown event is being sent
2. I hold A pressed, A type keydown events are still being sent
3. I press key B and keep it pressed, only B type keydown events are being sent (A is still pressed)
4. I release key B while A is still pressed, no keydown events are being sent

Steps to reproduce the bug

void keypress(Object sender, KeyRoutedEventArgs e)
{
           if (e.Key == Windows.System.VirtualKey.Up)
            {
               //doSmth
            }
            if (e.Key == Windows.System.VirtualKey.Down)
            {
               //doSmth;
            }
            if (e.Key == Windows.System.VirtualKey.Right)
            {
               //doSmth
            }
            if (e.Key == Windows.System.VirtualKey.Left)
            {
               //doSmth
            }
}

### Expected behavior

Keydown events are being generated for each pressed key, one key does not dominate the keydown event queue

### Screenshots

_No response_

### NuGet package version

WinUI 3 - Windows App SDK 1.1 Preview 2: 1.1.0-preview2

### Windows app type

- [ ] UWP
- [ ] Win32

### Device form factor

_No response_

### Windows version

Windows 10 (21H2): Build 19044

### Additional context

_No response_

[ojhad]

This is likely an IXP issue rather than a Xaml issue

[Hoffens]

Hi! Same problem here... @kevinguo305 Any news that u can share? Thanks!

[alienghub]

More than half a year has passed, still no solution. Definitely shows how WinUI is not a priority project for Microsoft.

[kevinguo305]

Hi all,

This behavior is as designed and how it's always functioned on the Windows platform SDK, which the Windows App SDK intends to stay consistent with. Can you explain to me what the desired behavior is and why you'd prefer that over the current behavior?

[wbic16]

The current behavior does not accurately reflect the input stream. The default SDK behavior works well for text, but falls apart for real-time events binding keystrokes to actions. Simple example: try to use a WPF KeyDown event handler to implement strafing in a 2D top scroller - you can only ever approximate the expected behavior (the user wants both inputs in this use case).