Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.20f1
2022.2.10f1
2023.1.0b8
2023.2.0a1
Issue ID
UUM-29608
Regression
No
Overlapping UI in UI Document Inspector Window
Repo steps:
- Go to Project Window > Right click > Create
- Hover on UI ToolKit > select UI Document
- UI Document should appear in the inspector window
- Resize the inspector window and observe
Expected Result: Numbers and values collapse and aren't visible
Actual Result: Numbers and values don't collapse and are visible
Reproducible with: 2021.2.19f1, 2021.3.21f1, 2022.2.0b16, 2022.2.11f1, 2023.1.0a26, 2023.1.0b8, 2023.2.0b6,
Could not test on: 2020.3.46f1 as this functionality does not exist
Platforms tested: Win 11, MacOS Monterey, Version 12.6.2
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future. In this specific case, the issue seems purely visual, not corrupting data and having a very limited UX impact.
Resolution Note (2023.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future. In this specific case, the issue seems purely visual, not corrupting data and having a very limited UX impact.