Dave Pearson

Dragging this into "in progress" and using this as a place to log some other issues with keys and Windows. See also [the problem with the default binding for the...

"Native" Windows, or under Parallels? I was able to recreate the shift issue yesterday with the latest Textual.

Just tested under "native" Windows and I'm seeing the exact same effects as I do when on my Mac under Parallels.

After experimenting while printing out the low-level values coming in via `win32.EventMonitor.run`, I'm noticing a couple or so things (this isn't a coherent set of facts yet, just observations to...

Following on from this, in the heart of the Win32 driver is this bit of code: ```python if ( key_event.dwControlKeyState and key_event.wVirtualKeyCode == 0 ): continue ``` If I'm reading...

If the above bit of code is extended with this: ```python or (key == "\x00" and key_event.wVirtualKeyCode != 50) ``` this *appears* to solve the problem[^1]. That is, it appears...

Moving this back to "in progress", as the scope for this has wandered a wee bit, and also there's some variation in how Windows behaves, it seems, that means any...

Bumping this over to "Blocked" for now; but something to keep in mind when we review #3411.

Not really; as this one is more about how the Windows driver can cope with the spurious NULs -- unrelated to unknown escape sequences and possibly-incorrect key names.

@geekscrapy You can `set_focus( None )`. For example: ```python from textual.app import App, ComposeResult from textual.widgets import Header, Footer, Input class RemoveFocusApp( App[ None ] ): BINDINGS = [ (...