Search Issue Tracker
By Design
By Design in 6000.3.X
Votes
0
Found in
2021.3.56f1
2022.3.66f1
6000.0.58f1
6000.2.4f1
6000.3.0b1
Issue ID
UUM-117392
Regression
No
Field is still marked as changed when changed back to its default state in UI Builder
Reproduction steps:
1. Create a new project
2. Create UI Document Asset (Create > UI Toolkit > UI Document)
3. Double-click on the newly created Asset to open UI Builder
4. Drag and drop Label Element to the Hierarchy
5. Make a change to a field in the Inspector (e.g. Enable Focusable option)
6. Unmake a change to a field manually (e.g. Disable Focusable option)
7. Observe the setting
Actual result: Field is still marked as changed
Expected result: Field is not marked as changed
Reproducible with: 2021.3.56f1, 2022.3.66f1, 6000.0.58f1, 6000.2.4f1, 6000.3.0b1
Reproduced on: Windows 11
Note: Field only stops being marked as changed after unsetting changes via kebab menu
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:
Setting the value of a style property or attribute in UI Builder is still considered as an override. It's a valid use case for users that want to make sure the UXML value is used no matter what. To revert to the initial value, you can use the Unset option in the context menu.
Resolution Note (6000.3.X):
Setting the value of a style property or attribute in UI Builder is still considered as an override. It's a valid use case for users that want to make sure the UXML value is used no matter what. To revert to the initial value, you can use the Unset option in the context menu.