Reproduction steps:
1. Open the attached “InputSystemTest.zip“ project
2. Connect the Xbox controller
3. Enter Play mode
4. Press “A” button on the controller and observe that “Raw button:“ and “Mapped button:“ change from “False” to “True”
5. Click on any other window other than the Editor and press the “A” button again
6. Observe the Game window

Expected result: “Raw button:“ and “Mapped button:“ change from “False” to “True”
Actual result: “Raw button:“ and “Mapped button:“ doesn’t change

Reproducible with: 1.7.0 (2022.3.45f1), 1.10.0 (2022.3.45f1, 6000.0.17f1)
Not reproducible with: 1.10.0 (2021.3.43f1)

Reproduced on: Windows 11 Pro, Xbox controller
Not reproduced on: macOS Sonoma 14.5 (Intel), Dualsense and Nintendo Switch Pro controllers

Notes:
- Regression is in Editor versions instead of the package versions
- Did not find FAV due to regression testing taking unreasonably too long
- Issue is reproducible when the controller is connected via Bluetooth and via cord
- Issue is reproducible with Xbox controller even though “Can run in the background:” is marked as “True”, but Dualsense and Nintendo Switch Pro controllers are marked as “False” but they can run in the background
- Relevant discussions link: [https://discussions.unity.com/t/input-system-not-receiving-input-when-focus-lost-with-correct-settings-in-editor-or-standalone/925339/10|https://discussions.unity.com/t/input-system-not-receiving-input-when-focus-lost-with-correct-settings-in-editor-or-standalone/925339/10|smart-link]