After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 762823 - [notebook] moving tabs with keys has no visual feedback
[notebook] moving tabs with keys has no visual feedback
Status: RESOLVED DUPLICATE of bug 762720
Product: gtk+
Classification: Platform
Component: Widget: GtkNotebook
3.19.x
Other Linux
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-02-28 16:23 UTC by Marinus Schraal
Modified: 2016-02-29 20:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marinus Schraal 2016-02-28 16:23:19 UTC 
Try moving notebook tabs with CTRL+Shift+PGUP/PGDOWN there is no visual feedback of the tab being moved to another position. However the tab does actually get moved: either move the mouse over the tabs or use CTRL+PGUP/PGDOWN to see the switch.
Comment 1 Matthias Clasen 2016-02-29 12:15:12 UTC 
I'm mystified - there is no ctrl-shift-pageup/down binding for reordering tabs.

Bindings for that are alt-left/right/up/down/home/end.

The only pageup/down bindings I see are

ctrl-pageup/down
ctrl-alt-pageup/down

which are for changing the current page
Comment 2 Marinus Schraal 2016-02-29 15:18:57 UTC 
Well, apart from those bindings working since I can remember (and those you suggest are not for me - are we talking about the same thing(?)), the same problem can be observed by right-clicking a tab and select 'move tab left/right'.
Comment 3 Matthias Clasen 2016-02-29 16:07:25 UTC 
I suggest that a bug observed in epiphany should be filed against epiphany. That saves a lot of this poking in the dark. If you file a gtk+ bug against GtkNotebook, I expect it to be reproducible in a testcase involving only that widget. This one isn't, since the bindings you talk about don't even exist there.
Comment 4 Michael Catanzaro 2016-02-29 20:40:28 UTC 
It's a regression in GTK+ 3.19. Probably bug #762720.

*** This bug has been marked as a duplicate of bug 762720 ***