Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.0-preview.7, 1.0.0-preview.1, 0.11.2-preview
Issue ID
1281302
Regression
No
[UI Builder] Properties are going out of the Canvas when Canvas resize to its minimum width and height
On resizing Canvas to its minimum width and height then properties go out of the Canvas under Viewport in the UI Builder window, Refer attached video.
Steps to repro:
1. Open attached Project
2. Window > UI Toolkit > UI Builder
3. Viewport > Canvas
4. Resize the width and height of Canvas
Actual Result:
Properties are going out of the Canvas on resizing it to its minimum width and height
Expected Result:
1. Properties name and input fields do not go out of the Canvas on resizing it
2. Horizontal and Vertical scrollbar should appear on resizing Canvas to its minimum width and height.
Note: UI Builder is introduced in the Unity 2019.2
Reproducible in:
2020.2.0b5, 2020.1.7f1, 2019.4.10f1, 2019.3.15f1, 2019.2.12f1 with package version 1.0.0-preview.7, 1.0.0-preview.1, 0.11.2-preview
Environment:
Occurring on Windows 10 & macOS 10.15.
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
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
Resolution Note:
This is not actually a bug. Elements going outside the boundaries of the Canvas need to remain visible to inform the user of problems if their UI document would be clones inside a smaller container. The Canvas serves as "fitter" for your UI. If things look wrong in the Builder, they will also look wrong in use.
We have considered adding a ScrollView to the Canvas but this adds too much ambiguity with user-created ScrollViews that are meant to take up the entire document. You would have a ScrollView within a ScrollView which is never a good workflow. ScrollViews also hide these potential fit problems and make it hard to work on the UI.
For large UIs, the recommendation is to increase the size of the Canvas and use the Viewport's Zooming and Panning to navigate the larger UI.
I've also added a task on our side to improve the look and feel of when an element leaks outside the Canvas so that it doesn't appear to be a bug (like it currently does).