Firefox/Projects/AcceleratedScrolling: Difference between revisions

Line 5: Line 5:


After implementing {{bug|462809}}, it became clear that we needed to be able to detect if the user already had an acceleration model {{bug|509651}} however, since that isn't in scope for 3.6, we are holding that bug and further investigation for 3.7 and moving forward with simply copying Chrome's behavior {{bug|513817}} for 3.6.
After implementing {{bug|462809}}, it became clear that we needed to be able to detect if the user already had an acceleration model {{bug|509651}} however, since that isn't in scope for 3.6, we are holding that bug and further investigation for 3.7 and moving forward with simply copying Chrome's behavior {{bug|513817}} for 3.6.
==Status==
*Currently the biggest concern is users who encounter double acceleration ([https://bugzilla.mozilla.org/show_bug.cgi?id=509651 bug 509651]), we need to also buy some mice that include their own driver with an acceleration model so that we can get a sense of what double acceleration feels like<br>
*Margaret has an initial implementation of an acceleration-based scroll model working on Windows
*The two thresholds we are now interested in experimenting with and tweaking are the:
**rate of acceleration
**time chunk of events to analyze before processing them
*Still looking for research and documentation in this general area of UI toolkit design
*Two patches are up for review that add the functionality described below


= Design: Acceleration Model for Scrolling =
= Design: Acceleration Model for Scrolling =
17

edits