Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.7f1, 2023.1.8f1, 2023.2.0b4, 2023.3.0a1
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0b2
2023.3.0a1
Issue ID
UUM-44453
Regression
No
Padding property value order is different compared to the USS property documentation when assigning values in the UI Builder Padding shorthand notation field
Reproduction steps:
1. Open the attached "CSS" project
2. Open the “Assets/Document.uxml” file
3. In the UI Builder Hierarchy window, click the “One” VisualElement
4. In the Inspector window, click the drop-down arrow next to Spacing
5. Click the drop-down arrow next to Padding
6. Observe the “1px 2px 3px 4px” Padding values
Expected result: Values are assigned the same way they are documented in the USS property documentation “Top: 1px, Right: 2px, Bottom: 3px, Left: 4px”
Actual result: Values are assigned “Left: 1 px, Right: 2px, Top: 3px, Bottom: 4px”
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Reproducible on: macOS Ventura 13.4.1 (M1 Max)
Note: In Unity version 2021.3.29f1, 2022.3.6f1, 2023.1.6f1 step 5. the “Spacing” name is “Margin & Padding”.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.3.0a1):
Fixed UUM-39648 @guillaume-riendeau:
UI Toolkit: Fixed exception thrown when adding a hidden column to a multi column control.