Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.66f1

6000.3.6f1

6000.4.0b7

6000.5.0a5

Issue ID

UUM-133282

Regression

No

"Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled

UI Builder

-

Steps to reproduce:

  1. Create a new Unity project using the Universal 3D template
  2. Create a new UXML document and open it in UI Builder
  3. Select the .uxml file in the Hierarchy
  4. In the Inspector or in the Viewport, change the Canvas Size Width/Height
  5. Click on the three dots in UI Builder and select "Reset UI Builder Layout"
  6. Observe that resetting does not affect Canvas Size
  7. In UI Builder Inspector, enable "Match Game View"
  8. Repeat the 5th step to reset the layout
  9. Observe the Canvas Size

Actual results: Resetting the UI Builder layout sometimes resets the Canvas Width/Height to a previous value (in this case, after the 9th step - to a random value) and sometimes does not reset the Canvas Size at all

Expected results: Resetting the UI Builder layout has consistent behavior with Canvas Size (either always resets Canvas Size to a specific value or never changes it)

Reproducible with versions: 6000.0.66f1, 6000.3.6f1, 6000.4.0b7, 6000.5.0a5

Tested on (OS): Windows 11

  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.