Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.8f1
2022.1
2022.2
Issue ID
1408548
Regression
No
OnEnable and OnDisable are called when minimizing the custom Editor window
Reproduction steps:
1. Open the user's attached "1167530-MaximizingWindow.zip" project
2. Open the "TestWindow" window (Window -> My Window)
3. See that "OnEnable" is called in the Console window
4. Drag and drop the "TestWindow" tab in the Tab Area of an existing window
5. Enable and disable the "Maximize" option for the "TestWindow" window (Right-click -> Maximize)
6. Observe the Console window
Expected result: OnEnable and OnDisable are not called
Actual result: OnEnable and OnDisable are called
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.14f1, 2022.1.0b10, 2022.2.0a7
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
- Template is opened in Isolation when opening it in Context and users Save the UI Document when prompted to do so in UI Builder
- 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
Resolution Note:
This is by design. When a window gets docked and undocked. It is possible the system serialize and deserialize the editor window.