Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.66f1

6000.3.5f1

6000.4.0b5

6000.5.0a5

Issue ID

UUM-132437

Regression

No

Cursor sometimes remains in resize state when dragging to the UI Builder “Add Class” window

UI Builder

-

Steps to reproduce:

  1. Create a new Unity project using a 3D Universal Template
  2. Create a UI Document (Assets > Create > UI Toolkit > UI Document)
  3. Double-click on it to open in UI Builder
  4. Add a Visual Element to the Hierarchy by dragging it
  5. Select the Visual Element and expand the "Text" foldout in Inspector
  6. To the left of the Size property, click on the three dots next to it
  7. Select "Extract Inlined Style to Selector" > "New Class…"
  8. Drag the cursor to the Add Class window
  9. Observe the cursor style

Actual results: The cursor briefly remains in the resize style (resize cursor)

Expected results: The cursor switches to the normal/default pointer instantly

Reproducible with versions: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5

Tested on (OS): Windows 11

Note: Does not matter what property is selected in the 6th step, just so that it has the "Extract Inlined Style to Selector" option

  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.