Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.2.15f1
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130248
Regression
No
UI Builder loses all progress or the .uxml file corrupts when entering a large value (8 digits) into properties that do not have clamped values
Steps to reproduce:
- Create a new Unity project using a 3D Universal Template
- Go to Assets > Create > UI Toolkit > UI Document
- Open the created .uxml in UI Builder
- Add any element to the Hierarchy (e.g. Label)
- In the Inspector, modify any of its properties for better change visibility (e.g. Scale, Color)
- In the Inspector, expand the "Transition Animation" foldout
- In the Duration property enter "10000000"
- Click File > Save, in the UI Builder
- Observe the UI Builder
Actual results: All made progress/changes in the UI Builder are lost and reset to default
Expected results: All fields should have clamped values and not allow such value to be saved
Reproducible with versions: 2023.1.0b1, 6000.0.64f1, 6000.2.15f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Tested on (OS): Windows 11, macOS 26.1 (M1 Pro)
Notes:
- The issue is reproducible in fields under "Filter", "Transition Animation" and "Transform" foldouts (possibly others as well)
- In 6000.2.15f1 version and below the .uxml file gets corrupted, while in 6000.3.2f1 and above, just the progress resets
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
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.
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.