Search Issue Tracker
By Design
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
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
- Scene and Game views break when the Editor window is snapped with the Microsoft PowerToys
- Materials do not transfer texture when the "Shader" parameter is changed from "Unlit/Texture" to "Universal Render Pipeline/Unlit"
- [Linux][Vulkan] Crash when opening searchable dialog
- The "Shader error in 'AE/Leaves': "Undefined punctual shadow filter algorithm"" error appears when build completes on a specific project
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.