Search Issue Tracker
Fixed
Votes
1
Found in [Package]
1.1.0-preview.2
Issue ID
1308116
Regression
No
New Input System's Mouse events get stuck on the first clicked UI Toolkit's Control
How to reproduce it:
1. Open the user's attached project "TextFieldSelection.zip"
2. Load "SampleScene"
3. Enter Play mode
4. In the Game view click on the first text field and notice that it gets highlighted
5. Click on the second text field
6. Observe the text field
Expected result: Second text field gets mouse input and it gets highlighted
Actual result: Second text field doesn't get mouse input and the first text field continues to consume mouse events
Reproducible with: 2020.2.5f1, 2021.1.0b7 (1.0.2, 1.1.0-preview.2)
Could not test with: 2018.4.31f1, 2019.4.19f1 (UI Toolkit is not introduced yet), 2021.2.0a5 (1.1.0-preview.2) - due to errors with UI Toolkit
Notes:
- Using UI Toolkit 1.0.0-preview.14 package
- Only reproducible when Active Input Handling is set to "Input System Package (New)"
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Should be fixed in the built-in version from the trunk (2021.2+). Could not be verified with the attached project.