Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.3.8f1

6000.4.0b8

6000.5.0a6

Issue ID

UUM-134163

Regression

No

Hierarchy dropdown buttons cut off Layer and Tag names instead of truncating names with ellipsis when column is set to smaller size

UI Toolkit Controls

-

Steps to reproduce:
1. Create new Unity project
2. Right-click on the header of the Hierarchy Window
3. Enable Layer Column
4. Create a Cube GameObject in Hierarchy window
5. Click on Cube GameObject Layer and from dropdown select “Add Tag...”
6. In Inspector window > Tags and Layers > open Layers
7. In “User Layer 10” add a layer name “PlayerNameLayerTesting”
8. Observe the Cube’s Layer dropdown in the Hierarchy

Actual results: When using longer Layer or Tag name, names gets cut off in Hierarchy’s dropdowns

Expected results: Longer Layer or Tag names should not be cut off, names are truncated with an ellipsis (…)

Reproducible with versions: 6000.3.8f1, 6000.4.0b8, 6000.5.0a6

Can’t test with versions: 6000.0.66f2 (New Hierarchy window is not available)

Tested on (OS): macOS Silicon Tahoe 26.2 (M1)

  1. 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.

  2. 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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.