Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.4.0b3
6000.5.0a3
Issue ID
UUM-131688
Regression
Yes
No visual separation of tabs in the "Packages Included" tab in Package Manager
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Package Management -> Package Manager -> Unity Registry -> 2D -> Packages Included
3. Observe the tab
Expected results: Package list and their descriptions are separated visually
Actual results: Package list and their descriptions are not separated visually
Reproducible with: 6000.4.0a2, 6000.4.0b3, 6000.5.0a3
Not reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0a1
Reproducible on: macOS Tahoe 26
Not reproducible 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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.