Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0b8
Issue ID
UUM-16347
Regression
Yes
[UIToolkit] "Nothing" flag gets set in the Enum flags field when earlier "Everything" flag was set
How to reproduce:
1. Open the user’s attached “UIToolkitBug” project
2. Open the “Scene” Scene
3. Select the “Bug” GameObject in the Hierarchy
4. Change the “Test (Component) → Example” field value to “Everything”
5. Re-select the GameObject
Expected result: Field value is set to “Everything”
Actual result: Field value is set to “Nothing”
Reproducible with: 2022.2.0a9, 2022.2.0b8
Not reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0a8, 2022.2.0b9, 2022.2.0b10, 2023.1.0a13
Reproduced on: macOS 12.5 (Intel), Windows 10
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:
Cannot reproduce in the latest 2022.2/staging. It seems this bug was fixed by https://github.cds.internal.unity3d.com/unity/unity/pull/16069
Resolution Note (2022.2.X):
Cannot reproduce in the latest 2022.2/staging. It seems this bug was fixed by https://github.cds.internal.unity3d.com/unity/unity/pull/16069