Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.5f1, 6000.2.0b3, 6000.3.0a1
Votes
0
Found in
6000.0.46f1
6000.1.0b14
6000.2.0a8
6000.3.0a1
Issue ID
UUM-102817
Regression
No
Non consistent "Editor Only" label position in the "Library" section
Steps to reproduce:
- Create a new project
- Go to Window -> UI Toolkit -> UI Builder
- Go to the "Library" section and click the kebab menu next to it
- Select "Editor Extension Authoring"
- Collapse all the sections "Containers", "Controls", 'Numeric Fields" and all others
- Observe the "Editor Only" label position
- Go to the same kebab menu and select "Tree View"
- Again, collapse all the sections
- Observe the "Editor Only" label position in this view
Actual results: "Editor Only" label position is messy and inconsistent with the previous view. A screenshot and video are added below in the "Attachments" section.
Expected results: Position should be stable and consistent.
Reproducible with versions: 6000.0.46f1, 6000.1.0b14, 6000.2.0a9
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): M1 Max - Sequoia 15.3.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
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
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.