Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.14f1
6000.4.4f1
6000.5.0b5
6000.6.0a3
Issue ID
UUM-140554
Regression
No
Open in Sprite Editor Button Label goes out of bounds when UI Builder's Inspector is resized to it's smallest size
Steps to reproduce:
- Open any Project
- Create a UIDocument Asset in the Project Browser and open it in UI Builder
- In the StyleSheets panel create a new USS and select the :root selector
- In the Inspector Variable list create an AssetReference Variable
- Change the Variable's Asset Reference Type to Sprite
- Reduce the UI Builder's Window to smallest possible and observe the "Open in Sprite Editor" button
Actual results:
Button label goes out of the button's bounds, unlike other buttons
Expected results:
Button text label is contained within the button
Reproducible with versions: 6000.3.14f1, 6000.4.4f1, 6000.5.0b5, 6000.6.0a3
Can’t test with versions: 6000.0.73f1 (No Variables in selector)
Tested on (OS): Windows 11
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
- Some post-processing volume overrides only update after a refresh when using HDRP
- Video Player glitches when Skip On Drop is enabled
- GameObject movement in Scene view becomes stuttery and intermittently freezes when using non-standard pointers across editor tabs or window boundaries
- Addressables.CheckForCatalogUpdates() always returns 0 when "Only update catalogs manually" is enabled
- VFX Graph forces a lengthy recompilation freeze when exiting Play Mode with a cloned Render Pipeline asset
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.