Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.1.4f1
2020.2
Issue ID
1273031
Regression
No
Errors and inability to interact with window when docked and redocked
Reproduction steps:
1. Open attached project "Charts.zip"
2. In Menu, open Test/Test Window
3. Dock the Test Window above the Game View
4. Observe Console window
5. Dock the Test Window next to the Inspector window
6. Observe and try to close/interact with the previous and current positions of the Test Window
Expected results: No errors, ability to interact with and close the Test Window
Actual result: "ObjectDisposedException" console error, inability to interact, only closes after second "Close Tab" action
Reproducible with: 2019.4.10f1, 2020.1.6f1, 2020.2.0b3
Could not test with: 2018.4.27f1 (console errors break project)
Notes:
1. When relaunching Unity, the "ghost" window, docked above the Game View, loads without problem
2. Repositioned Test Window closes after the second "Close Tab" action
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
- 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
Resolution Note:
UI Elements are not persisted (nor their data or states) so it's up to the user to ensure the survival of associated data. UI Elements are always recreated so you cannot rely on them to survive a domain reload or a simple recreation.