Search Issue Tracker
By Design
Votes
0
Found in
6000.0.30f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-90230
Regression
No
UI Toolkit ScrollView.verticalPageSize doesn't change the scrolling amount when using keyboard arrows
Steps to reproduce:
1. Open the attached “ScrollViewBug.zip” project
2. Open the “SampleScene”
3. Enter Play Mode
4. Click on the Scroll Bar
5. Use the arrow keys to move the Scroll Bar
6. Observe the amount of scrolling done by each keypress
Expected result: The Scroll Bar moves the same amount as pressing the up or down arrow above or below the Scroll Bar and is moved the same amount as ScrollView.verticalPageSize is set to
Actual result: The Scroll Bar moves slowly and is never influenced by ScrollView.verticalPageSize
Reproducible in: 6000.0.30f1, 6000.1.0a7
Couldn’t test in: 2022.3.53f1, 2021.3.46f1 (because versions didn't have “INotifyBindablePropertyChanged” and “UxmlElement Attribute”)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- The tag adder functionality does not work if a space is entered instead of a name
- Errors thrown in the Console when configuring In-App Purchases package
- Longer Scaler Profile names go out of the"Scaler Profilers" section
- AI Navigation window UI elements overlap when the AI Navigation window is docked and resized
- Editor freezes after some time when using NavMeshQuery::Raycast
Resolution Note:
Hi,
This is by design, to move by the page size we expect you to use the PageDown and PageUp keys.
The slider supports the following keys:
Arrow keys - Move by 1/100 of the entire range
Arrow keys + shift - Move by 1/10 of the entire range
Home - Go to start of slider
End - Go to end of slider
PageUp - move up by 1/100 of the entire range multiplied by the page size
PageDown - move down by 1/100 of the entire range multiplied by the page size
Ill speak to our documentation team and make sure this information is available.
Thanks for the bug report!