Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.21.8
Issue ID
ADDR-3325
Regression
No
Addressables Report window can be resized in a way that restricts access to its parts
Steps to reproduce:
1. Open a new project and install the Addressables package
2. Open Window>Asset Management>Addressables>Addressables Report
3. Resize the window to a sufficiently small size
Expected result: scrollbars would appear or the minimum size would be restricted to a certain value
Actual result: sections of the window are hidden with no way to access them
Reproducible with: 1.21.3, 1.21.9
Note: Earlier versions of the package do not have the Addressables Report window. 1.21.3 was not available in the "Affects Version/s" field thus 1.21.8 was used.
Editor versions tested: 2020.3.47f1, 2022.2.15f1, 2023.2.0a10
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (1.21.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.