Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.68f1

6000.3.10f1

6000.4.0b9

6000.5.0a7

Issue ID

UUM-134961

Regression

No

Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected

Inspector Framework

-

Steps to reproduce:

  1. Create a new Unity project using the Universal 2D template
  2. Create a new Triangle Sprite (Assets > Create > 2D > Sprites > Triangle)
  3. Select the newly created Triangle Sprite
  4. Click the "Open Sprite Editor" button in the Inspector window
  5. Change the Sprite "Name" property to something that's very long in the Sprite Editor window
  6. Click the "Apply" button in the Sprite Editor window
  7. Expand the Triangle asset by pressing an arrow on the right of its icon in the Project window
  8. Select the renamed Sprite in the Project window
  9. Observe the Inspector window

Actual results: Sprite name labels are overflowing and are not truncated both in the Inspector window and the Preview section

Expected results: Sprite name labels are truncated

Reproducible with versions: 6000.0.68f1, 6000.3.10f1, 6000.4.0b9, 6000.5.0a7

Tested on (OS): MacOS Silicon Tahoe 26.2

  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.