Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2020.3.40f1
2021.3.12f1
2022.1.17f1
2022.2.0b8
2023.1.0a12
Issue ID
UUM-18701
Regression
No
The value in the Inspector field is highlighted on MouseUp() rather than MouseDown()
How to reproduce:
1. Open the attached project “NumericInput”
2. Open the “SampleScene” scene
3. Select “GameObject” GameObject
4. Click on any field on the Transform Component, then clean the selection by clicking anywhere outside the field
5. Click on this field again without releasing the mouse button
Expected result: The value in the field is highlighted
Actual result: The value is not highlighted and will be highlighted once you release the mouse button
Reproducible with: 2020.3.40f1, 2021.3.12f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a12
Reproducible on: Windows 11 Pro
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Closing this as designed since it's the behavior that is expected for select all on mouse up. Please note that modifying the nature of this use case would introduce an unwanted user experience. Lastly, it is worth mentioning that the UI is being migrated to use UI Toolkit where this behavior was not reproduceable.
Resolution Note (2023.1.X):
Closing this as designed since it's the behavior that is expected for select all on mouse up. Please note that modifying the nature of this use case would introduce an unwanted user experience. Lastly, it is worth mentioning that the UI is being migrated to use UI Toolkit where this behavior was not reproduceable.