Closed
Bug 536280
Opened 16 years ago
Closed 4 years ago
Cannot immediately navigate to top or bottom of page using scroll region on trackpad
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: lukpac, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b5) Gecko/20091204 Firefox/3.6b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b5) Gecko/20091204 Firefox/3.6b5
In FF 3.5, rapidly moving up or down in the scroll region on a trackpad results in navigation to the top or bottom of a page, similar to using the Home and End keys. This no longer works in FF 3.6.
If the page isn't too long, up/Home may still work, but down/End almost never works. On longer pages up/Home will be broken as well.
Reproducible: Always
Steps to Reproduce:
1. Quickly move finger up or down in the trackpad scroll region.
Actual Results:
The page will scroll up or down, but not necessarily to the top or bottom of the page.
Expected Results:
The top or bottom of the page should have been scrolled to, as if Home or End was pressed.
Trackpad driver is Synaptics v10.1.8 06Dec07
| Reporter | ||
Updated•16 years ago
|
Version: unspecified → 3.6 Branch
Blocks: 507222
| Reporter | ||
Comment 1•16 years ago
|
||
Also, to clarify, I have not (yet, anyway) tried earlier versions of 3.6 or any version of 3.7. I can probably try if necessary, though.
| Reporter | ||
Comment 2•16 years ago
|
||
This continues to be an issue in 3.6 final.
| Reporter | ||
Comment 3•16 years ago
|
||
This appears related to https://bugzilla.mozilla.org/show_bug.cgi?id=543511. With 3.6.2, acceleration down seems to be the same as acceleration up, but the scroll region is still not emulating Home/End like it was pre-3.6. mousewheel.acceleration.start is set to -1.
| Reporter | ||
Comment 4•16 years ago
|
||
I'm trying 4.0b1 now. There does not appear to be a change in the behavior.
Here's a good example page:
http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/
Quickly flicking from one edge of the scroll area to the other will only scroll the page about 1/4 of the total page height. In 3.5 such a flick would navigate to the top or bottom of the page.
| Reporter | ||
Comment 6•15 years ago
|
||
This continues to be an issue in 4.0b4.
| Reporter | ||
Comment 7•15 years ago
|
||
This continues to be an issue in 4.0b6.
| Reporter | ||
Comment 9•15 years ago
|
||
"...broken in 4.0b7."
| Reporter | ||
Comment 10•15 years ago
|
||
This continues to be an issue in 4.0.1.
Comment 11•15 years ago
|
||
Reporter -> Are you still experiencing this issue with the latest version of Firefox 5? Does the issue occur with the latest nightly? http://nightly.mozilla.org/
What type of trackpad are you using? What driver version? Have you updated the driver/software to the latest releases?
| Reporter | ||
Comment 12•15 years ago
|
||
The behavior did not change in 5.0. I have not tried any nightly builds.
The mouse CP shows it as "Synaptics TouchPad V5.9 on PS/2 Port". Driver is v10.1.8 06Dec07. The newest version on Gateway's site is 7.12.3.0, which is from 2005.
I was able to get 15.2.20 31Mar11 from Synaptics' site. With this driver, and setting mousewheel.acceleration.start to 0, "scroll to top/bottom" more or less works again, although the behavior is different from what it was in 3.5 and earlier. From what I can tell, older versions of FF implemented this behavior directly. The way it is working now seems to be via the "Enable Inertia" setting in the driver. With the old way, the behavior was literally like pressing Page Up/Down. With "Enable Inertia", the page simple scrolls to the top or bottom very fast.
It would be nice if the pre-3.6 behavior could be brought back.
Comment 13•4 years ago
|
||
Marking this as Resolved > Worksforme since the issue is no longer reproducible on Firefox Nightly 96.0a1 (2021-11-19), beta 95.0b8 or release 94.0 on a Lenovo Yoga Windows 10.
If anyone can still reproduce this issue please re-open it or file a new one.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•