463201 - Using mouse wheel should scroll tab list

Status: RESOLVED WONTFIX

(Firefox :: Tabbed Browser, enhancement)

Description

[Olli Pettay [:smaug][[e-mail]]]

It could be useful to be able to scroll the tab list using mouse wheel.

Comment 1

[Dão Gottwald [:dao]]

In terms of moving the selection to the next item, moving event.detail items forward, or going to the next page?

Comment 2

[Ed Lee :Mardak]

Potential issue is that ctrl-mousescroll on OS X is the default binding for zooming in/out of the screen (OS zoom).

Comment 3

[Dão Gottwald [:dao]]

(In reply to comment #2)
> Potential issue is that ctrl-mousescroll on OS X is the default binding for
> zooming in/out of the screen (OS zoom).

When the panel is sticky (e.g. after clicking the button in the tab bar or focusing the search field), Ctrl isn't needed anymore. As long as Ctrl is pressed, I'd hope that OS X would just not forward the event to the application.

Comment 4

[Dão Gottwald [:dao]]

Attachment: go to the next / previous page

Comment 5

[Ed Lee :Mardak]

Somewhat related.. I wonder if the mouse gestures can be used for the tab list...

Hrmm.. does the browser window stopping propagation prevent the panel from getting it? Would we want to mix gesture commands with context sensitive behavior?

Seems like switching pages with swipes could make sense. But OS X's task switcher dialog uses mouse-scroll to switch through applications.. and it doesn't really separate things by pages.

Comment 6

[Dão Gottwald [:dao]]

(In reply to comment #5)
> Somewhat related.. I wonder if the mouse gestures can be used for the tab
> list...
> 
> Hrmm.. does the browser window stopping propagation prevent the panel from
> getting it?

Yes. gGestureSupport could add the listener to "document", so other consumers like the ctrlTab code could still add a listener to "window" in order to consume the event earlier.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Do we really want to jump a whole page forward/backward? IMO it's more helpful to jump to the next/previous tab preview. Having e.g. only one page makes the mouse wheel useless.

Comment 8

[Ed Lee :Mardak]

(In reply to comment #6)
> Yes. gGestureSupport could add the listener to "document", so other consumers
> like the ctrlTab code could still add a listener to "window" in order to
> consume the event earlier.
I just played around with various configurations, and gGestureSupport doesn't need to change. It's using capture at the window level, so ctrlTab or extensions can also add event listeners at the same level with capture true.

Comment 9

[Dão Gottwald [:dao]]

(In reply to comment #7)
> IMO it's more helpful to jump to the next/previous tab preview.

You'd still have to move the mouse and click or use your keyboard to actually select the preview. So that's not really useful.

(In reply to comment #8)
> I just played around with various configurations, and gGestureSupport doesn't
> need to change. It's using capture at the window level, so ctrlTab or
> extensions can also add event listeners at the same level with capture true.

But then gGestureSupport would still listen to the same event, right?

Comment 10

[Ed Lee :Mardak]

(In reply to comment #9)
> But then gGestureSupport would still listen to the same event, right?
Yup. Stopping an event at a certain level doesn't prevent other listeners at the same level from getting the event.

Comment 11

[Dão Gottwald [:dao]]

Bug 465076 removed the pages from the all tabs view -> wontfix.