Closed
Bug 657648
Opened 14 years ago
Closed 14 years ago
Don't use high resolution scrolling when acceleration is enabled
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
VERIFIED
FIXED
mozilla6
Tracking | Status | |
---|---|---|
firefox6 | - | --- |
People
(Reporter: jmjjeffery, Assigned: masayuki)
References
Details
(Keywords: regression, Whiteboard: nominated by dao without comment)
Attachments
(1 file)
2.42 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
This patch seems to have turned off scrolling acceleration. Used to be the faster you rolled the wheel the further the page would scroll, now it seems linear/flat no matter how fast you roll the wheel. For those that used this feature it 'feels' like scrolling is now way slower.
Acceleration works: http://hg.mozilla.org/mozilla-central/rev/3e7a21049b6c
Does not work: http://hg.mozilla.org/mozilla-central/rev/0a1e7ec7e268
Modified prefs to set acceleration to user liking, these prefs were in use before bug 605648 landed so I know it was working:
mousewheel.acceleration.factor;5
mousewheel.acceleration.start;3
Prior to landing I can scroll page in one roll of the wheel. With this patch those settings seem to be ignored or over-written, as it takes 2-3 rolls to scroll the same page.
I have tried turning off the pref: mousewheel.enable_pixel_scrolling
No effect.. scrolling is still not accelerated.
Tried doubling mousewheel.withnokey.numlines;24 and no effect, still no acceleration.
If there is no way to return to, or enable accelerated scrolling with wheel, then the page will/could have an undesirable affect on end-users. I know I'm not liking the change, but I also know you cannot make everyone happy.
Reporter | ||
Updated•14 years ago
|
Keywords: regression
Updated•14 years ago
|
tracking-firefox6:
--- → ?
Assignee | ||
Comment 1•14 years ago
|
||
Disables high resolution scrolling if acceleration is enabled.
# we can disable high resolution scrolling by failing the query event handling in ESM.
Comment 2•14 years ago
|
||
Comment on attachment 533195 [details] [diff] [review]
Patch v1.0
Hmm, why do we have the acceleration, if it is disabled by default?
r=me anyway.
Attachment #533195 -
Flags: review?(Olli.Pettay) → review+
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #2)
> Hmm, why do we have the acceleration, if it is disabled by default?
On Windows, we cannot know whether the active mouse utility have its owning acceleration or not. If a system had it and enabled it, the scrolling speed is accelerated twice (by utility and us). And not all users want acceleration.
Furthermore, even if we could know the system information, we couldn't compute good speed because user may set the scrolling speed faster for non-acceleration environment.
Anyway, acceleration makes different behavior from other applications. Many users don't want such difference on their desktop.
http://hg.mozilla.org/mozilla-central/rev/b8a035ebdf0f
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Summary: Mouse acceleration settings no longer respected since bug 605648 → Don't use high resolution scrolling when acceleration is enabled
Target Milestone: --- → mozilla6
Reporter | ||
Comment 4•14 years ago
|
||
Verified fixed, thanks for the quick turn-around.
Tested on cset: http://hg.mozilla.org/mozilla-central/rev/caba046161e5
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 5•14 years ago
|
||
Did you testes with "mousewheel.enable_pixel_scrolling" true?
Now, high resolution scrolling is disabled in default settings.
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #5)
> Did you testes with "mousewheel.enable_pixel_scrolling" true?
>
> Now, high resolution scrolling is disabled in default settings.
No I did not, but I just now re-tested, and scrolling is still accelerated with the pref set to 'true'
Assignee | ||
Comment 7•14 years ago
|
||
Thank you for your testing and report!
Updated•14 years ago
|
Whiteboard: nominated by dao without comment
Updated•14 years ago
|
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•