Search Issue Tracker
Won't Fix
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2021.3.36f1
2022.3.21f1
2023.2.15f1
6000.0.0b11
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-67709
Regression
No
Editor.OnEnable is called twice when its InspectorElement is placed inside another InspectorElement
Reproduction steps:
1. Open the attached “InspectorElement.zip” project
2. Open the Test Window (Sheriff->TEST Window)
3. Make sure the Scene Window is active
4. In the Test Window click the button labeled "Click"
5. Observe the Console
6. Now make sure the Inspector Window is active instead of the Scene Window
7. In the Test Window click the button labeled "Cleanup" and repeat 4th step
8. Observe the Console
Expected result: On both occasions, the "ChildScriptableEditor.OnEnable" only appears once
Actual result: When the Inspector Window is not active the “ChildScriptableEditor.OnEnable" appears twice
Reproducible with: 2021.3.36f1, 2022.3.21f1, 2023.2.15f1, 6000.0.0b11
Reproducible on: Windows 11
Not reproducible on: no other environment tested
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.