Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.5.0b8

6000.6.0a5

Issue ID

UUM-142128

Regression

No

Two previews are visible at once and overlap when reducing the expanded preview size in Object Selector windows

Inspector Framework

-

Steps to reproduce:

  1. Create a new 3D URP proejct
  2. In the Hierarchy, select any GameObject
  3. In the Inspector, click on the cube icon to modify the GameObject's icon
  4. Select "Other..."
  5. In the opened window select any texture
  6. Resize the texture preview from the highest size to smaller
  7. Observe the behavior

Actual results: The previously expanded preview and the resized preview are visible at the same time for a brief moment during the transition

Expected results: Only one preview should be visible during the resize transition, with no overlap between preview states

Reproducible with versions: 6000.5.0b8, 6000.6.0a5

Can’t test with versions: 6000.3.15f1, 6000.4.6f1, 6000.6.0a3 (preview would not expand to such bigger size)

Tested on (OS): Ubuntu 24.04, macOS 26.4

Notes:

  • Reproduces with all object pickers in the Editor
  • On macOS and Windows it seems more like a timing issue, and changing the preview size fast reproduces the issue
  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.6.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.