GNOME Bugzilla – Bug 167693
Tabs should slide over (sometimes) when adding a new tab
Last modified: 2018-04-15 00:18:59 UTC
Distribution/Version: Gentoo 1. Open a bunch of pages in different tabs. More than enough room for, so you get those "<" and ">" arrows on the ends. 2. Go to the last tab (e.g. the right most one). 3. Middle-click on a link to open it in a new tab. 4. Notice how you have to click the ">" icon to go to that tab. It would be very nice if, when you opened a tab, from a link in the last tab, to slide the tabs over, so the user won't have to click that ">" icon. Thanks :)
This is actually a nice idea, however the change is needed in GTK. Basically when we call gtk_notebook_insert_page() gtk should attempt to scroll the notebook so that the newly added tab is visible, while of course ensuring that the current tab is still visible.
Any chance this could be implemented in 2.10?
We keep getting bug reports about this in Epiphany...
*** Bug 300537 has been marked as a duplicate of this bug. ***
Still an issue as far as I'm concerned in 3.20.2. Starting with an instance of Web with 8 tabs open (max before they start to get pushed off the main page). When ctrl clicking a link or using the context menu to open a link in a new tab from the rightmost tab, there is no evidence that the action succeeded thus introducing confusion. This could be alleviated by forcing the stack of tabs to shift left by one. Focus can still be kept on the originating tab, but the new tab would be shown to spring up and be loading. Something like this would prevent people like from from ctrl clicking 6 times wondering what happened only to discover that the action worked and now I have 5 superfluous tabs.
Just an FYI: we agree and understand that this is an annoying problem. We have some more complex designs for improving our tabs situation here: https://wiki.gnome.org/Design/OS/Tabs/
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