Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.4.0b5
6000.5.0a4
Issue ID
UUM-131696
Regression
No
"Runtime" and "Editor (for Editor Extension Authoring) fields are rendered inconsistently compared to other settings fields in the same window
Steps to reproduce:
- Create a new Unity project
- Create a new Unity Default Runtime Theme (Create > UI Toolkit > Unity Default Runtime Theme File)
- Rename the newly created file to a longer title
- Open "Project Settings" (Edit > Project Settings)
- Select the "UI Toolkit" and find the "Project Preview Theme" section
- Verify that the newly created theme title is displayed in the "Runtime" and "Editor (for Editor Extension Authoring) fields
- Resize the window and observe how these two fields are rendered compared with all other fields in the same window
- Dock the "Project Settings" window next to the "Game" field
- Observe how these two fields are displayed in a docked view
Actual results: In Project Settings → UI Toolkit, the Runtime and Editor Theme fields are rendered inconsistently compared to other settings fields in the same window. These fields use a different layout behavior, extending into the right side of the panel and creating excessive space, misalignment, or an oversized field area.
Expected results: In Project Settings → UI Toolkit, the Runtime and Editor Theme fields should be rendered using the same layout rules as all other settings fields in the window. Long theme titles should be truncated with "...".
Reproducible with versions: 6000.4.0b3, 6000.5.0a4
Tested on (OS): macOS - Tahoe 26.2
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
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
Resolution Note:
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.
Resolution Note (6000.5.X):
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.