Search Issue Tracker
By Design
Votes
0
Found in
2022.0.1
Issue ID
1434172
Regression
Yes
EditorWindow.minSize not used properly when an EditorWindow is docked.
This issue has no description.
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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Resolution Note:
This is by design. This change was made on purpose. The problem with respecting the minSize of a Window when docked is that it makes it very difficult to resize other docked windows. It was also always a lie anyway, since if you had 2 windows docked side by side with each a minSize, one of them would still be smaller than its minSize to all the other one to respect its minSize. This setup would result of wild snapping as each window would try to force its own minSize onto others.