Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a13
2019.1.1f1
2019.2.0a1
2019.3.0a1
Issue ID
1152014
Regression
Yes
UIElements button text is offset vertically towards the top when using the "Personal" Editor Skin
How to reproduce:
1. Open the attached project "UIElementsExamples-2019.1.1f1"
2. Make sure your Editor Skin is set to "Personal" under Preferences
3. Click UIElementsExamples -> 7_EditorControls at the top of the Editor to open an example window
4. Observe all of the button text positionings on the right-hand side of the window
Expected result: button text is centered vertically with equal padding from the top of the button boxes as from the bottom
Actual result: button text is positioned slightly closer to the top than it is to the bottom (Can compare to see how it should be with the "IMGUI Container" region on the left)
Reproducible with: 2019.1.a013, 2019.1.2f1, 2019.2.0b1, 2019.3.0a2
Could not test with 2019.2.0a12 (The mentioned UI Elements window region is squished and completely unusable)
Note:
-The reproduction project is from the UI Elements example project GitHub page https://github.com/Unity-Technologies/UIElementsExamples
-It might be the case that the text is at the correct absolute vertical position, but the button bounding boxes are all shifted slightly down
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (2019.3.X):
Closing this as "Will not fix", minor defect and can be worked around. Getting high user pain because it is flagged as a regression, but a very minor one. With that said, we are going to review the styles with the uss variables in the near future.