GNOME Bugzilla – Bug 377441
Make notebook arrows scroll the tab view
Last modified: 2018-12-10 15:28:06 UTC
Arrows of the too-many-tabs-for-window-width state should behavior like arrows of menus, allowing auto-smooth-scrolling when the mouse is over it.
I fully agree. Having used firefox 2 this afternoon, I can say this behaviour of smooth-scrolling the tabs is way more predictable than the current way the arrows work. In fact, when you click on the arrow on the side of the tab list, you intuitively expect that the next hidden tab will appear. In practice it doesn't, but the tab next to the current one is selected. This just makes the notebook a pain to use when there are too many tabs to fit in the notebook width.
Please could this issue be looked at, there really is an important usability problem with GtkNotebook for apps like browsers and editors where the user has too many tabs to fit on screen. (I work on the Geany editor and often people on the mailing list complain about the lack of scrolling in the notebook.) The current switch to tab left/right buttons really are not useful as the user can just click on the tab instead or use a keyboard shortcut - making these buttons scroll the notebook tabs would be much more useful, and perhaps more intuitive for most users. I think the way Firefox 2 does it is that after scrolling, if the user hasn't selected one of the tabs that has been scrolled in view, and the current tab is no longer visible, then scroll the view back after a timeout to show the current tab on screen. BTW, perhaps this bug could be renamed to 'Make notebook arrows scroll the tab view' to be clearer.
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new
Reported again at: https://gitlab.gnome.org/GNOME/gtk/issues/1506