Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.19f1
2023.1.0b18
2023.2.0a17
2023.3.0a3
Issue ID
UUM-36953
Regression
No
Filters dropdown: Window doesn't rescale on items collapse
Steps to reproduce:
- Create/open any project
- Go to the "Window" menu item and select "Package Manager"
- In the "Package Manager" window find the "Filters" dropdown
- Observe that accordingly to the stream it should have "Status" or "Status" and "Categories" dynamic fold-out sections
- Try to collapse them and expand them and observe the window
Expected Result: Filters menu window should rescale as foldouts are collapsed/expanded (as it is implemented in a Scene window section). Added video in the "Attachments" section from the "Package Manager window and Scene window
Actual Result: Filters menu window doesn't rescale when its items are collapsed. Added video in the "Attachments" section.
Reproducible with: 2022.2.0a2, 2022.2.19f1, 2023.1.0b18, 2023.2.0a17
Not Reproducible with: 2021.3.26f1 as this stream has no "Filters" dropdown
Confirmed OS: MacOS Monterey, Version 12.6.5
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note:
After careful consideration, we've decided not to fix this bug at this time due to its minimal impact on overall functionality. Our resources are currently focused on addressing critical bugs, new features. If this issue significantly impacts your experience, feel free to reach out to us again, and we'll be happy to explore alternative solutions or workarounds
Resolution Note (2023.3.X):
After careful consideration, we've decided not to fix this bug at this time due to its minimal impact on overall functionality. Our resources are currently focused on addressing critical bugs, new features. If this issue significantly impacts your experience, feel free to reach out to us again, and we'll be happy to explore alternative solutions or workarounds