Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

6000.0.72f1

6000.3.13f1

6000.4.3f1

6000.5.0b4

6000.6.0a2

Issue ID

UUM-139304

Regression

No

Restoring Vector Image Asset type breaks UI Builder Background Image reference

UI Builder

-

Reproduction steps:
1. Create a new project
2. Import a Vector Image Asset and  create UI Document (Create > UI Toolkit > UI Document)
3. Double-click UI Document to UI Builder window and drag and drop VisualElement to UI Builder Hierarchy
4. Change Background Image type to “Vector” and select imported Vector Image Asset
5. Change the Vector Image Asset type to “Texture2D” in the Inspector and click “Apply” button
6. Change the Asset type back to “UI Toolkit Vector Image” and click “Apply” button again
7. Observe the UI Builder

Actual result: Vector Image Asset icon disappears and the {}“{}Select Vector Image” window shows “None” as the selected option
Expected result: Same option is selected and displayed in both Image field and “Select Vector Image” window

Reproducible with:  2023.3.0a2, 6000.0.72f1, 6000.3.13f1, 6000.4.3f1, 6000.5.0b4, 6000.6.0a2

Reproduced on: macOS Tahoe 26.3 (M4)

  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.