Search Issue Tracker
In Progress
Fix In Review for 6000.4.X
Votes
0
Found in
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-100773
Regression
Yes
The height of grand child is not correctly computed when mixing different flex-directions and flex-grow
Steps to reproduce:
- Create a UI document
- Open it in the UI Builder
- Select the root element in the Hierarchy pane
- In the inspector, check "Editor Extension Authoring"
- In the toolbar of the viewport, change the theme to "Active Editor Theme"
- Create a VisualElement and name it "V0"
- Sets V0's position = absolute
- Add a child VisualElement to V0 and named it "V1".
- Sets V1's flex-direction = row, width = 200px and height = 100px
- Add a child VisualElement to V1 and named it "V2".
- Sets V2's align-self = flex-start and {}flex-grow=1{}.
- Add a Label to V2 with some text and named it "V3"
- Set the label's flex-grow=1
- Verify the resolved height of V0, V1, V2, V3 using "Window/UI Toolkit/Debugger":
Here are steps to use UIToolkit Debugger with the UI Builder:
- In UIBuilder, click the Preview button on the toolbar of the viewport.
- Open the UI Toolkit Debugger from ""Window/UI Toolkit/Debugger".
- Select "Builder" in the Panel dropdown in the toolbar of the Debugger window.
- Click the "Pick Element" button
- Pick the element you want to inspect in the UIBuilder window.
Note: You can directly use the attached uxml file to save some time.
Actual results:
The heights of V0, V1, {color:#de350b}V3{color} 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 {color:#de350b}V3{color} 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.
!image-2025-06-13-08-44-50-343.png|width=444,height=410!
Reproducible with versions: 6
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment