Closed
Bug 160280
Opened 22 years ago
Closed 10 months ago
Scrolling speed should increase when scrollbar button is held down
Categories
(Camino Graveyard :: General, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
Future
People
(Reporter: rcarr, Unassigned)
Details
Chimera build ID: 2002073005
OS version: OSX 10.1.5
I've noticed that in other OS X apps, when a scroll up or down button is held
down, after a couple of seconds the scrolling speed increases slightly. In
Chimera however, it scrolls at a constant speed no matter how long the button is
held down. I think it should behave the same way as other applications in this area.
Confirmed using Chimera/20020724. Using TextEdit, scrolling speed gradually
increases, while Chimera's remains constant.
However, BBEdit 6.1.2 behaves as Chimera. Is this a Carbon vs. Cocoa issue?
Updated•22 years ago
|
Summary: Scrolling speed should increase when scroll button is held down → [RFE] Scrolling speed should increase when scroll button is held down
Comment 2•22 years ago
|
||
Not really (except for maybe on the method of implementation level -- might be
easier in Cocoa). Some apps utilize accelerated scrolling, some don't. It was
like this already in the Mac OS 8 & 9 days. I was actually surprised to see this
reported on Bugzilla...
Updated•22 years ago
|
Summary: [RFE] Scrolling speed should increase when scroll button is held down → Scrolling speed should increase when scroll button is held down
Comment 3•22 years ago
|
||
*** Bug 177954 has been marked as a duplicate of this bug. ***
Comment 5•22 years ago
|
||
i'm sure that we scroll slowly enough that we're dominated by gecko scrolling
logic and not the OS. short of making our scrolling logic faster, i'm not sure
what to do here.
Updated•22 years ago
|
Summary: Scrolling speed should increase when scroll button is held down → Scrolling speed should increase when scrollbar button is held down
Comment 6•22 years ago
|
||
I think Chimera is the only browser that scrolls one line at a time for each
click of the scrollbar arrow button. MSIE does 4 at a time, OmniWeb has what the
initial bug reporter is asking for. IMO any time you're going to be holding the
arrow buttons down for a long enough period of time for the incremental scroll
speed boost you'd be better off grabbing the thumb and moving it yourself, but
it'd be easy to have it move multiple lines at a time and that'd improve the
perceived scrolling speed.
Off topic a bit, this method of scrolling viewed through the glaring microscope
of Quartz Debug with Autoflush drawing turned on (which bypasses the double
buffering so you can see more clearly what is being drawn to the buffer) results
in some pretty ugly drawing - try using the up arrow button, what's up with that?.
This drawing weirdness is probably related to bug 164234, which seems to only be
noticable on 10.2, but fixing these weird drawing habits would make Chimera
scroll faster across the board. That being said, Chimera's scroll speed seems
pretty good in spite of this on 10.2 using the Logitech mouse driver and the
mouse wheel.
Comment 7•22 years ago
|
||
i think all we can do is improve our scroll speed, and that's already covered by
bug 164234. closing this as a dupe.
*** This bug has been marked as a duplicate of 164234 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Pink, are you sure this is a dupe? This bug wasn't about scrolling being slow,
it's about wanting scrolling to *accelerate* as the scroll button is held down.
Reopening, I think my comment 8 is correct.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 10•20 years ago
|
||
Enhancement. Targeting for Future. Priority 5.
Severity: normal → enhancement
Priority: -- → P5
Target Milestone: --- → Future
Mass-reassign of bugs still assigned to pinkerton to nobody; filter on "NoMoPinkBugsInCamino".
Assignee: mikepinkerton → nobody
Status: REOPENED → NEW
QA Contact: winnie → general
Status: NEW → RESOLVED
Closed: 22 years ago → 10 months ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•