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
- UI Toolkit Editor Window Creator becomes deformed and stretched when the “Enter” key is pressed
- “Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console when changing Trail GameObject position to a very high number
- VFX Graph Node documentation icon is pixelated
- Cutout box is covered in a shadow when the object that houses the cutout is casting shadows
- “Metal: Fragment shader missing texture binding at index 0 (_MainTex / Hidden/Preview Alpha)” warnings are thrown when selecting some TextMesh Pro Font Assets
Resolution Note:
This is by design. When a window gets docked and undocked. It is possible the system serialize and deserialize the editor window.