Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1131885
Regression
No
Maximizing Scene View throws errors when having a docked custom EditorWindow with a different name than It's script file name
How to reproduce:
1. Open the user-submitted project ("BugRepro.zip")
2. Click on Test/Window and dock its Window
3. Maximize and Minimize the Scene Window twice
4. Observe the Console Window
5. Close and reopen the Project
6. Observe that the Custom Window is now gone and a Warning has been thrown in the console
Expected result: maximizing the scene window does not affect the custom editor and it is still docked properly when restarting Unity
Actual result: after maximizing the scene window with the custom editor docked the editor throws the "NotImplementedException" error on the first time and then the "Invalid editor window UnityEditor.FallbackEditorWindow" error on the subsequent times
Reproduced in: 2019.2.0a7, 2019.1.0b5, 2018.3.7f1, 2017.4.22f1
Note: The first "NotImplementedException" error does not reproduce on the 2019.2 and 2019.1 versions
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 (2019.2.X):
low priority defect, likely won't be fixed.