Search Issue Tracker
Won't Fix
Won't Fix in 2021.2.X
Votes
1
Found in
2020.3.9f1
2021.1.8f1
2021.2.0b1
Issue ID
UUM-2522
Regression
No
Last line of pixels of images are not visible in Project Window when using One Column Layout
How to reproduce:
1. Open attached project "case_1340449_lastLine.zip"
2. Observe "imagetest-oneline" and "imagetest-twoline"
3. Change Project Window layout to "One Column Layout"
Expected result: Last line of pixels does not dissapear when the layout is changed
Actual result: Last line of pixels is not visible when the layout is changed
Reproducible with - 2018.4.35f1, 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a18
Comments (1)
-
eMsylf
Jun 03, 2021 15:24
After further investigation I found the issue also applies to the Project view's Two Column Layout when zoomed out to the smallest setting.
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 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 (2021.2.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.