Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.1f1
Issue ID
833966
Regression
Yes
Horizontal Scroll View with Elastic Movement Type works differently upon changing the resolution of game window
Horizontal Scroll View with Elastic Movement Type inside a Canvas with Canvas Scaler set to "Scale with screen size" behaves differently when changing the game window resolution to different one from the one set in Reference Resolution of Canvas Scaler.
To reproduce:
1. Open the attached project
2. Set game window resolution to 480x800
3. Enter play mode
4. Notice that it is possible to drag the white image so that it covers the whole game window
5. Change the resolution to 320x480
6. Notice that it is no longer possible to drag the white image so that it covers the whole game window as it leaves some space on the right
Expected: Scroll View works the same no matter the resolution of the game window when Canvas Scaler is set to "Scale with screen size"
Actual: Scroll View works differently depending on the resolution of the game window when Canvas Scaler is set to "Scale with screen size"
Note:
Different resolutions produce different results. For example setting the game window to 1024x768 allows the image to leave outside the bounds
Reproduced on: 5.4.1p1, 5.4.1f1, 5.4.0f3
Not reproducible on: 5.3.6p5, 5.2.5f1
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 warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
This is a duplicate of issue #827908