Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.11f1, 2023.1.15f1, 2023.2.0b10, 2023.3.0a4
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0b2
2023.3.0a1
Issue ID
UUM-43504
Regression
No
Vector3Field SetValueWithoutNotify triggers RegisterValueChangedCallback when used with float.NaN
Reproduction steps:
1. Open the “NaNVectorNotify_Stripped” project
2. Choose the Window menu > NaN Test
3. Click “Set to NaN” and observe the Console
Expected result: RegisterValueChangedCallback is not fired because SetValueWithoutNotify is used
Actual result: “RegisterValueChangedCallback…” was logged
Reproduced in: 2021.3.0f1, 2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Reproduced using: macOS 13.4.1 (c) (Intel), Linux 5.15.0 Ubuntu 22.04.2 (by reporter)
Notes:
1. Not reproduced with an individual FloatField
2. Could not test in runtime because Vector3Field is specific to the Unity Editor UIElements system
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2023.2.0b10):
Fixed UUM-43504 @laila-chammaa:
UI Toolkit: Fixed Vector3Field SetValueWithoutNotify triggers RegisterValueChangedCallback