Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.3.3f1

6000.4.0b3

6000.5.0a4

Issue ID

UUM-131605

Regression

No

Help boxes in Advanced Text Settings are misaligned on the right side of the UI Builder Inspector window

UI Toolkit Controls

-

Steps to reproduce:

  1. Create a new Unity project
  2. Create a new UI document(Project window ->Create ->UI Toolkit -> UI Document (UXML))
  3. Double-click it
  4. Add "Text Field" component
  5. Make the "Inspector" window wider
  6. Find and expand the "Text" section in the "Inspector" window
  7. Observe the displayed help box under the "Advanced Text Settings" 
  8. Select the "Advanced" item in the "Text Generator Type" dropdown
  9. Observe the newly displayed help box, which should appear below the "Text Generator Type" field

Actual results: Help boxes are not aligned on the right side

Expected results: Help boxes should be aligned with all other fields in the "Inspector" window.

Reproducible with versions: 6000.3.3f1, 6000.4.0b3, 6000.5.0a4

Tested on (OS): macOS - Tahoe 26.2

Notes: The same help box alignment issue exists with the help box, which is displayed below the "Scale Mode" field in the "Background" section. The right side of the help box should be aligned with other fields.

  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.