Closed Bug 242745 Opened 20 years ago Closed 20 years ago

trackpoint scrolling support broke between firefox 20040503 and 20040504

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 242799

People

(Reporter: jellis, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a) Gecko/20040505 Firefox/0.8.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a) Gecko/20040505 Firefox/0.8.0+

Scrolling using the trackpoint and third button on Thinkpads (the blue button
between or below the two red ones) works great in Firefox 20040501 and prior,
but it does not work in 20040505.  I'm using a Thinkpad T23.

Bug 20618 seems to be a catchall for these issues, but it has been open for some
time.  The problem I am describing *was* fixed until just recently, so I think
it must be a different issue and a regression.

Reproducible: Always
Steps to Reproduce:
1. Launch Firefox 20040505
2. Bring up a webpage that is too long for the screen (e.g., slashdot.org)
3. Hold down the blue trackpoint button (cursor turns into scroller icon)
4. Move the trackpoint down and up
Actual Results:  
Page does not scroll down and up

Expected Results:  
Page should scroll down and up, as it did in Firefox 20040501
confirming

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040505
Firefox/0.8.0+
installer build, no extensions

using an IBM T40p laptop with latest 7.5.17.8 UltraNav driver installed. 
Scrolling works in every other application the way it should.
In the MZ forum http://forums.mozillazine.org/viewtopic.php?t=74129 a workaround
(for Synaptics) is to set the "scrolling selection" to "Scroll item under
pointer" instead of "Scroll selected item".

This makes the bug sound like a focus thing to me. (the content area is not the
'selected' item, so it doesn't scroll)

Could be a result of bug 242111, as that bug appears to have caused bug 242560
(difficulty with focusing with the mouse)...

David

PS- I cannot currently confirm this bug exists (no nightly on my laptop).
I can confirm that on IBM thinkpad the trackpoint (aka ultranav) scrolling is
broken since the 2004/05/05 build.  The trackpoint has 3 scrolling modes that
can be selected in the control panel:
- standard: broken for firefox and thunderbird works for everything else.
- smooth: work for firefox if you enable autoscroll but does not work most
windows application (other than IE and MSOffice).
- auto-detect: cannot detect which mode is supported by firefox and get stuck on
the last selected mode.
Confirming on Firefox 2004-05-07. I have ThinkPad R40, and TrackPoint UltraNav
drivers. As a temporary workout, switching scrolling mode to "smooth" from the
UltraNav control panel, this bug goes away. That mode is completely stupid
though. I hope this gets fixed soon.
I downloaded a few builds to narrow down the date this bug arose.  The last
Firefox build Trackpoint scrolling works for me in is 20040503.  20040504 is the
first to exhibit this bug.
This bug does look to be caused by this checkin by bryner:

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2004-05-03+14%3A47&maxdate=2004-05-03+14%3A49&cvsroot=%2Fcvsroot

Based on the regression window given in comment #5

bryner: was this you?

-> Event Handling
Assignee: general → events
Component: Browser-General → Event Handling
QA Contact: general → ian
Slightly clarifying summary and adding myself to CC (both of which I forgot to
do earlier)

Sorry for the bugspam
Summary: trackpoint scrolling support broke between firefox 20040501 and 20040505 → trackpoint scrolling support broke between firefox 20040503 and 20040504

*** This bug has been marked as a duplicate of 242799 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.