Search Issue Tracker
Active
Under Consideration for 1.15.X
Votes
0
Found in [Package]
1.15.0
Issue ID
ISXB-1706
Regression
No
Newly created Input binding enters rename mode when it is created while the Action is in rename mode
Reproduction steps:
1. Create a new project and install the Input System package
2. Right-click in the Project Window and select Create > Input Actions
3. Open the newly created .inputactions asset
4. Create a new Action Map
5. Create a new Action (by pressing the + icon or right-click > Add Action)
6. While Action is in rename mode, right-click on it and select “Add Binding”
7. Observe the binding
Expected result: The binding is not in rename mode
Actual result: The binding is in rename mode
Reproducible with: 1.13.0 (6000.0.35f1), 1.14.0, 1.15.0 (6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1)
Reproducible on: Windows 11
Not reproducible on: no other environments tested
Note:
- Before 1.13.1 version (1.13.0 and below), only the selected binding would turn into rename mode and clicking another binding would turn that binding into rename mode, but would remove that state from the previous binding. However, in 1.13.1 and newer, clicking other bindings turns all of them into a rename state
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment