GNU bug report logs - #32002
24.4; Scroll bar start, end not correct

Previous Next

Full log

Message #115 received at 32002 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Mike Kupfer <mkupfer <at> alum.berkeley.edu>, Robert Pluim <rpluim <at> gmail.com>
Cc: 32002 <at> debbugs.gnu.org, npostavs <at> gmail.com, kurn <at> sfu.ca
Subject: Re: bug#32002: 24.4; Scroll bar start, end not correct
Date: Sat, 07 Jul 2018 09:17:24 +0200

> Here's a possible way to test: if you have a mouse with multiple
> buttons, right-click in the scrollbar above or below the thumb (slider).
> Based on my testing, that appears to be equivalent to clicking on a
> stepper button (with GTK3).

The areas above and below the thumb (or slider), if they exist, serve
for jumping to the buffer position corresponding to the position
clicked at.  It's only natural that this results in a "jump" - where
calculating the new position of an object in a window relates the
position of the mouse cursor on the associated scroll bar and the size
and position of the thumb to the overall size of the object.

The arrow keys serve a completely different purpose: They support line
by line (or column by column) scrolling and are, in practice, used
only when the area reserved for the scroll bar is too small to
accommodate a thumb or the user has no mouse wheel in order to scroll
a window.  Pressing an arrow key results in a "step" - where the
calculation of the new position of an object in a window is based on
its old position plus/minus a fixed number of lines/columns or pixels.

Please keep these two concepts apart when suggesting how people should
test the behavior of their scroll bars.

Thanks, martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.