Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X
Votes
0
Found in
2019.2.0a11
2019.3.0a1
2019.3.0a9
Issue ID
1169663
Regression
Yes
Window scaling ignores set maxSize value
How to reproduce:
1. Open the attached project ("maxsizeissue.zip")
2. Go to "QuickTool" -> "Open"
3. Observe that the window is not scalable (This is expected, the minSize and maxSize values are set to the same Vector2 value)
4. Press "My Button"
5. Try to scale the window (The maxSize is set to a slightly higher value while the minSize remains the same)
Expected result: the window is now scalable but only to a certain, small, set maxSize
Actual result: the window is now scalable but the max size is unlimited
Reproduced in: 2019.3.0a9, 2019.2.0b10, 2019.2.0a11
Not reproducible in: 2019.2.0a10, 2019.1.11f1
Couldn't test with: 2018.4.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment