Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.11.2
Issue ID
ISXB-1171
Regression
Yes
Fields of certain types in the Input Actions Editor take two clicks to select when editing a different field
How to reproduce:
1. Open the attached “IN-88201” project
2. In the Project tab, open the “test” Input Actions
3. Under the “a” Action, select the “Custom” binding
4. In the Binding Properties tab, select the input field of the “Float Parameter”
5. Select the checkbox of the “Bool Parameter”
6. Observe the result
Expected result: The “Bool Parameter” is selected
Actual result: The “Bool Parameter” is not selected
Reproducible in: 1.8.0-pre.1 (2022.3.52f1), 1.11.2. (2022.3.52f1, 6000.0.26f1, 6000.1.0a3)
Not reproducible in: 1.7.0 (2022.3.52f1), 1.11.2 (2021.3.45f1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Regression happened when the interface was updated. 1.11.2 is unaffected in 2021.3.45f1 because it uses the old interface
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
Resolution Note:
Modifying or changing focus on composite bindings in the Input Actions Editor no longer causes a full UI rebuild
Resolution Note:
Modifying or changing focus on composite bindings in the Input Actions Editor no longer causes a full UI rebuild