Search Issue Tracker
Fixed in Fixed in trunk
Votes
0
Found in [Package]
1.0.0-preview.5
Issue ID
1281537
Regression
Yes
[UI Builder] A child's and next in Hierarchy item variables swap when saving UI Document after changing the child's Border Width
How to reproduce:
1. Open the attached "VariableSwap" project
2. Create a new UI Document (in the project window right-click->Create->UI Toolkit->UI Document) and open it
3. From the UI Builder Library add two VisualElement and one Button elements
4. Move the added Button to be a child of the VisualElement which is first in the Hierarchy
5. In the UI Builder Hierarchy select the Button
6. In the UI Builder Inspector expand the Border section
7. In the UI Builder Inspector change the Width to 5px
8. Save the UI Document (in the Viewport File->Save)
Expected results: No errors are thrown, the changed variable does not get switched with the element next in the Hierarchy
Actual results: The "Accessing invalid property" error is thrown, the changed variables on the Button get switched with the second VisualElement
Reproducible with: 1.0.0-preview.5, 1.0.0-preview.9 (2019.4.13f1, 2020.1.10f1, 2020.2.0b8, 2021.1.0a2)
Not reproducible with: 1.0.0-preview.4 (2019.4.13f1, 2020.1.10f1, 2020.2.0b8, 2021.1.0a2)
Could not test with: 2018.4.28f1 because the UI Builder package was not yet introduced
Notes:
- Only the variables that were changed before saving are swapped
- The variables get swapped between the child and the next in the Hierarchy that is at the same level as the child's parent
- Sometimes saving the UI Document before the last step will prevent the issue from reproducing
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 locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Resolution Note (fix version Fixed in trunk):
The issue has been fixed in the engine and not package. Fixed in 2021.2.0a4