Search Issue Tracker
Fixed in 2021.3.32f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a8
Votes
1
Found in
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a15
2023.3.0a3
Issue ID
UUM-35758
Regression
No
Rename Shortcut Profile window does not display all the data correctly
Steps to reproduce:
- Open the Shortcuts window (Edit>Shortcuts for Windows or Unity>Shortcuts for Mac)
- Click on the Profiles dropdown
- Click Create New Profile
- Enter a profile title that is close to the maximum allowed character amount and click Create
- Click on the Profiles dropdown again
- Click Rename Profile
- Observe the window
Expected result: All the info in the window should be displayed fully and tidily.
Actual result: Info is overlapped. Added screenshot in the "Attachments" section.
Reproducible with: 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a15
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2023.3):
Thank you for reporting this issue. It has been fixed for the latest version of Unity.
Resolution Note (fix version 2023.2):
Thank you for reporting this issue. It has been fixed.
Resolution Note (fix version 2023.1):
Thank you for reporting this issue. It has been fixed.
Resolution Note (fix version 2022.3):
Thank you for reporting this issue. It has been fixed.
Resolution Note (fix version 2021.3):
Thank you for reporting this issue. It has been fixed.