Search Issue Tracker
Active
Under Consideration for 1.15.X
Votes
0
Found in [Package]
1.15.0
Issue ID
ISXB-1748
Regression
No
wasPressedThisFrame always returns false on macOS when Caps Lock is enabled
How to reproduce:
- Open the “UnityInputTest.zip“ project
- Open the “main“ Scene
- Enter Play Mode
- Enable Caps Lock
- Press the “a“ key on the keyboard
- Observe the Console
Expected result: Three logs are triggered simultaneously (1. “aKey.wasPressedThisFrame“, 2. “anyKey.wasPressedThisFrame“, 3. “anyKey.wasPressedThisFrame“ + “aKey.wasPressedThisFrame“)
Actual result: Only one log is triggered (1. “aKey.wasPressedThisFrame“)
Reproducible in: 1.3.0 (2023.1.0a1), 1.15.0 (6000.0.61f1, 6000.2.10f1, 6000.3.0b8, 6000.4.0a3)
Reproduced on: macOS 26.0.1 (M1 Max)
Not reproduced on: Windows 11, No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment