[StrangePan][2.1.12] on MacOS, numpad keys send navigation inputs
Posted: Mon Jul 20, 2026 7:12 pm
This appears to be caused by the fix for this bug report: 133992.
On the apple magic keyboard with numpad, there is no concept of numlock. The navigational keys are separate from the numpad. It seems like the fix above, for apple keyboards on macOS, is interpreting a numpad key as a navigational key and a number input. This causes havoc with number input fields. 0 and 5 work as expected. The rest of the digits undo the highlight of the text before typing, causing you to add digits to the number instead of replacing it. 4 and 6 in particular move the cursor, so typing most numbers with those digits is nearly impossible with the numpad. For example, typing 1234 results in 1243, and leaves the cursor between the 4 and 3.
Expected result: numpad navigational inputs should be ignored entirely on macos. At very least, they should be ignored on keyboards that don't have a numlock status, like the magic keyboard with trackpad.
On the apple magic keyboard with numpad, there is no concept of numlock. The navigational keys are separate from the numpad. It seems like the fix above, for apple keyboards on macOS, is interpreting a numpad key as a navigational key and a number input. This causes havoc with number input fields. 0 and 5 work as expected. The rest of the digits undo the highlight of the text before typing, causing you to add digits to the number instead of replacing it. 4 and 6 in particular move the cursor, so typing most numbers with those digits is nearly impossible with the numpad. For example, typing 1234 results in 1243, and leaves the cursor between the 4 and 3.
Expected result: numpad navigational inputs should be ignored entirely on macos. At very least, they should be ignored on keyboards that don't have a numlock status, like the magic keyboard with trackpad.