GNOME Bugzilla – Bug 332491
Wrong seeking direction when using the scroll wheel
Last modified: 2009-02-17 12:36:45 UTC
IMHO the right action when you scroll the mouse wheel up should be to rewind and fast forward when you scroll down. Right now totem behaves the opposite way.
In Epiphany bug 306110 and evince bug 309236 it was decided that scroll-up == 'In' and down == 'out', so the current up=forward, down=rewind seems consistent with that.
See also bug 164351 for Rhythmbox, bug 330570 which I reassigned from Totem. The bottom line is that it's a matter of taste, and I'd rather not change the behaviour now.
*** Bug 351634 has been marked as a duplicate of this bug. ***
My bug has just been makred duplicate of this one. I'm kind of shocked to see this one flagged as wontfix. I urge you to reconsider fixing this bug. I paste my reasoning from the other issue: seeking forward should be the action when scrolling down - since that matches the behaviour of the scrollwheel every else. In documents you scroll down to see what comes next (not what was written before) If you like to see it from an "interaction with the widget" view instead of a "action that should be performed" view: When using the scrollweheel over an horizontal scrollbar, it moves to the right, not to the left - so should the handle of the seekbar.
"The bottom line is that it's a matter of taste". No it's not. It's not a matter of Totem vs. RB, it's a matter of Totem vs. every other gnome app, that is, consistency. I'll quote myself from the bug I just filed in Launchpad: "Just open an image on EOG, zoom in to make the sliders appear, hover the button over the horizontal one and scroll down. See what happens? Every other app is consistent with that behavior, save Totem". I think Christian is right and the fact that he didn't get a reply in over a month just proves it IMO. Why should Totem's seekbar's behaviour be opposite to any other scrollbar in the whole OS?
*** Bug 518707 has been marked as a duplicate of this bug. ***
*** Bug 532121 has been marked as a duplicate of this bug. ***
*** Bug 564039 has been marked as a duplicate of this bug. ***
*** Bug 572109 has been marked as a duplicate of this bug. ***