Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a3
2019.1.0a1
2019.1.8f1
2019.2.0a1
2019.3.0a1
Issue ID
1172459
Regression
Yes
Inconsistent Editor window layout when switching between docked and floating window modes
How to reproduce:
1. Open the user-submitted project
2. Open a Custom Editor window (Nementic -> Prefab Replacer)
3. Make the Prefab Replacer window small enough for the horizontal and vertical scrollbars to appear
4. Inspect the layout of the Prefab Replacer window in floating mode
5. Dock the Prefab Replacer window and resize it to a similar size as before
6. Inspect the layout of the Prefab Replacer window in docked mode
Expected result: Layout is the same for both docked and floating window modes
Actual result: Layout is different for docked and floating window modes
Reproducible with: 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Notes:
Issues are reproducible with standard Unity Editor windows as well. However, custom layouts in these windows make some issues invisible.
Window header box is cut on the left side while in floating mode (reproducible in 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11)
Scrollbars have a part of them cut off while in docked mode (reproducible in 2019.1.13f1, 2019.2.0f1)
Window content has a bigger gap from the top in floating mode (reproducible in 2018.4.5f1, 2019.1.13f1, 2019.2.0f1)
Window header has a larger gap from the left side while in docked mode (reproducible in 2019.1.13f1, 2019.2.0f1, 2019.3.0a11)
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
Resolution Note (2019.3.X):
low priority for our team, unlikely to be fixed for the moment.