Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
1.0.0-preview.17
Issue ID
1361779
Regression
No
[UI Builder] UI elements are out of alignment when creating them with UI Builder
Reproduction steps:
1. Open user's attached project "UIBuilderBugs.zip"
2. Open Assets > Scenes > Sample Scene
3. Double click on "NewUXMLTemplate" found in Assets, to open UI Builder
4. Observe the alignment
5. Switch UI Builder theme to "Default" and observe
6. Switch to GameView and observe the alignment
Expected results: "UI Builder" elements are aligned
Actual results: "UI Builder" elements are out of alignment
Reproduced in: 1.0.0-preview.12 ( 2020.3.18f1), 1.0.0-preview.17 ( 2020.3.18f1, 2021.1.22f1, 2021.2.0b12, 2022.1.0a10)
Could not test with: 2019.4.30f1 ( UI Builder is not introduced yet)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Current alignment issues are unfortunately by design, as alignment was not reliably included in the design requirements. We need to refactor some of the designs (UX) and adjust the UI Builder if needed. Unfortunately, we have a finite capacity and an established roadmap, especially on the UX design front. While we understand this is causing issues today, we can only convert it into a design feature request. Resolved (Postponed)