Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.2.15f1
6000.3.2f1
6000.4.0b2
6000.5.0a3
Issue ID
UUM-130358
Regression
No
Dragger elements from Slider controls doesn't scale and stay outside minimized Canvas window in UI Builder Viewport in UI Builder
Steps to reproduce:
1. Create new Unity project
2. Open UI Builder window (Window > UI Toolkit > UI Builder)
3. From Library add Slider, SliderInt and MinMaxSlider to the Hierarchy
4. In Viewport resize Canvas to small size
5. Observe Dragger elements in Viewport
Actual results: When Canvas window is minimized, Dragger elements stay in Viewport
Expected results: When Canvas window is minimized, Dragger elements should also get minimized accordingly to the Canvas window size
Reproducible with versions: 6000.0.64f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b2, 6000.5.0a3
Tested on (OS): Ubuntu 24.04, macOS Tahoe 26.1 (M1)
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 Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" 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.