Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.3.X
Votes
0
Found in
6000.3.8f1
Issue ID
UUM-134741
Regression
No
"Custorm" typo is written in Asepct Ratio Dropdown when a custom value is entered
How to reproduce:
- Create and open a new project
- Create and open a new UI Document in the Project tab
- Drag a Visual Element into the UI Builder’s Hierarchy
- Select the Visual Element, and in the UI Builder’s Inspector navigate to Size → Aspect Ratio
- Change the value to anything numerical, and observe the dropdown to the left of the field
Actual result: “Custorm“ is written
Expected result: “Custom” is written
Reproducible in: 6000.3.9f1, 6000.4.0a1
Not reproducible in: 6000.4.0b9, 6000.5.0a7
Could not test in: 6000.0.68f1 6000.2.0a10 (Aspect Ratio is not available)
Fixed in: 6000.4.0a2
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.3.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.