Not signed in
Copyright © 2026 Unity Technologies
Will wait for users to encounter this before we act. Might be too much of a corner case and we cannot risk layout changes right now.
Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Given the highly risky nature of UITK layout code changes causing further regressions, I'm cancelling the 6.2 port. We may re-open later if, after the fix is implement, we decide it's safe enough.
Steps to reproduce:
Here are steps to use UIToolkit Debugger with the UI Builder:
Note: You can directly use the attached uxml file to save some time.
Actual results:
The heights of V0, V1, V3 are around 100px whereas V2's height is around 15px/17px(font size)
Expected results:
The heights of V0, V1 are around 100px whereas the height of V2 and V3 are around 15px/17px (font size)
8:28
Note that the expected results is based on what we should expect from html/css specs as the image below shows. However, before this regression, the actual result was not even the right one neither but at least it was not causing the linked bug. In previous version, the result was : The heights of V0, V1, V2, V3 are all around 100px, which was not right neither.
Reproducible with versions: 6
Notes:
Sign in to see your voted issues