Search Issue Tracker
Fixed
Fixed in 6000.0.60f1, 6000.2.6f1, 6000.3.0a3
Votes
1
Found in
2022.3.63f1
6000.0.51f1
6000.1.6f1
6000.2.0b5
6000.3.0a1
Issue ID
UUM-109513
Regression
Yes
Inspector field does not revert to mixed value on Undo when new value matches the second objects original value
How to reproduce:
1. Open the “IN-104601_MixedValueBugs“ project
2. Select “ExampleA“ and “ExampleB” in the Project window
3. In the Inspector change the “Number” mixed value to “1”
4. Undo the action (Ctrl + Z)
5. Observe the “Number” value
Expected result: The field is updated and displays the mixed value as dash (—)
Actual result: The field is not updated and stays as “1”
Reproducible with: 2022.3.63f1, 6000.0.0b13, 6000.0.51f1, 6000.1.6f1, 6000.2.0b5
Not reproducible with: 2022.2.0a8
Could not test with: 2022.2.0a9, 6000.0.0b12 (Different issue is present where trying to modify the field automatically inputs “0” or when you input “1” it is greyed out and does not change the value preventing accurate reproduction)
Reproducible on: macOS 15.5 (M1 Max), Windows 11 (by user)
Not reproducible on: no other environments tested
Note: This issue does not reproduce if you change the number to a value different than the “ExampleB” asset number
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment