Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.72f1
6000.3.12f1
6000.4.1f1
6000.5.0b1
6000.6.0a1
Issue ID
UUM-138058
Regression
No
UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Create a new Editor window (Assets > Create > UI Toolkit > Editor window)
- Enter a very long name into the c# name field
- Click the "Confirm" button
- Observe the UI Toolkit Editor Window Creator
Actual results: The UI Toolkit Editor Window Creator is not interactable and greyed out
Expected results: There is either a character limit to not go over the maximum name limit or some other fallback
Reproducible with versions: 2023.1.0a3, 6000.0.72f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Tested on (OS): MacOS Silicon Tahoe 26.3
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thanks for the bug report. We unfortunately don`t have the bandwidth to fix issues resulting from invalid or unreasonable input. We will consider doing a batch of fixes related to these kind of issues in the future, but we cannot accept this bug right now.
Resolution Note (6000.6.X):
Thanks for the bug report. We unfortunately don`t have the bandwidth to fix issues resulting from invalid or unreasonable input. We will consider doing a batch of fixes related to these kind of issues in the future, but we cannot accept this bug right now.