Search Issue Tracker

Won't Fix

Won't Fix in 6000.6.X

Votes

0

Found in

2022.3.63f1

6000.0.50f1

6000.1.7f1

6000.2.0b5

6000.3.0a1

6000.4.0a1

6000.5.0a1

6000.6.0a1

Issue ID

UUM-108785

Regression

No

Actions in UI Builder Preview mode are not fully reset after exiting the Preview mode

UI Builder

-

Steps to reproduce:

  1. Open the attached project
  2. Open the Test UI Document
  3. Enter Preview mode
  4. Enter a value in the TextField
  5. Exit the Preview mode

Actual results: Changes to the placeholder text carry over from the Preview mode

Expected results: Changes made in the Preview mode are reset after the user exits the mode

Reproducible with versions: 2022.3.63f1, 6000.0.50f1, 6000.1.7f1, 6000.2.0b5

Tested on (OS): macOS 15.5

Notes:

  • The placeholder text value gets reset after exiting the Preview mode and then selecting the object manually
  • If {}.unity-base-text-field{}{}input--placeholder{} selector is overridden, changes from the Preview mode remain even after using the above-mentioned workaround. To fully reset the object user needs to enter the Preview mode for the second time and focus the affected object (Preview_Reset_2 reference video)
  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.