Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.2.9f1
2023.1.0b4
2023.2.0a4
Issue ID
UUM-29721
Regression
No
Scheduling interrupts user input when using UIToolkit Input Fields
Steps to reproduce:
1. Open the attached project “IssueProject“
2. Open the “Assets/Test Scene.unity“ Scene
3. Enter Play Mode
4. Start typing into any input field
Expected result: Scheduling does not interrupt input action
Actual result: Focused field is updated by the schedule method
Reproducible with: 2022.2.9f1, 2023.1.0b4, 2023.2.0a4
Couldn’t test with: 2020.3.45f1, 2021.3.19f1 (couldn’t resolve “Element 'UnityEngine.UIElements.FloatField' has no registered factory method.“ error)
Reproducible on: Windows 10
Note: Look at the attached video for clarity
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We acknowledge there is a UX discrepancy, and that the value of the field itself should change while the text being edited should not. However, we think that this is a very infrequent problem that can potentially be worked around.
We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We acknowledge there is a UX discrepancy, and that the value of the field itself should change while the text being edited should not. However, we think that this is a very infrequent problem that can potentially be worked around.
We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.