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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
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.