Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a8
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1119610
Regression
Yes
Window with UI Elements breaks on refresh after a script recompilation
How to reproduce:
1. Open the attached "UIElementsBug.zip" project
2. In Project window, double-click the "New Behavior" asset to open a custom window
3. In the opened window, click one of the "Action" labels
4. Open one of the foldouts (e.g. Parameters)
5. Reimport BehaviorEditorWindow.cs script
Expected result: The "New Behavior" window stays unchanged.
Actual result: After reimporting the script, UI of the "New Behavior" window is broken.
Reproducible with - 2018.3.0a8, 2018.3.3f1, 2019.1.0a1, 2019.1.0b1, 2019.2.0a2
Not reproducible with - 2018.3.0a7
Note: Not tested on 2017.4 due to compile errors.
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note (2019.2.X):
The issue occurs by usage of the VisualElement.clippingOptions = ClippingOptions.ClipAndCacheContents.
This feature is being removed as we transition out of experimental and now offer a batch renderer which makes this less useful.
The best suggestion right now is to stop using the caching functionality in 2018.X until migration to 2019.X.