Search Issue Tracker
Not Reproducible
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
Issue ID
UUM-111776
Regression
Yes
Visual Element fails to encapsulate its children when a child element has "flex-grow" set to 1
How to reproduce:
1. Open the “IN-108266“ project
2. From the Project window open the "DynamicLayoutExample2.uxml" file
3. Observe the “ContentBox2” Visual Element border
Expected result: Parent element fully encapsulates its children
Actual result: Parent element fails to fully encapsulate its children
Reproducible with: 6000.0.0b13, 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Not reproducible with: 2023.3.0b10
Could not test with: 6000.0.0b11, 6000.0.0b12 (The child element with "flex-grow: 1" does not expand, could not test bug behaviour)
Reproducible on: macOS 15.5 (M1 Max), Windows 10
Not reproducible on: no other environments tested
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
I don't see what the bug is. Looking through all the styles, the system is doing what it's supposed to. It's given absolute widths, text, and conflicting width/height+flex-grow styles and this is the end result. It's difficult to tell from the description of the bug what the expectation is (ie. which parent? which child?) or how this is different from standard flexbox.