GNOME Bugzilla – Bug 672427
GtkNotebook does not use GtkWidget window-draggable property
Last modified: 2018-02-10 03:32:40 UTC
I can unmaximize Web by pulling down on any whitespace in the toolbar but not the copious whitespace in tab bar (to the right of the rightmost tab).
This is because window-dragging does not work in GtkNotebook. I was playing with this today but I can not get the drag/grab to work properly. Something is preventing 'release' from being emitted. Works: click-n-drag Does not work: click-n-drag, release, click-n-drag (without moving the cursor) Someone who actually knows GTK+ should be able to fix this. Also, don't know if you actually want this to be more like OSX where any "empty" chrome is a draggable point. Think a Preferences dialog. It's full of empty chrome.
Moving to GTK+.
Created attachment 210760 [details] [review] WIP: make GtkNotebook window-draggable
> Also, don't know if you actually want this to be more like OSX where any > "empty" chrome is a draggable point. Think a Preferences dialog. It's full of > empty chrome. Windows are already draggable everywhere, if you are willing to hit the Super key.
(In reply to comment #4) > > Also, don't know if you actually want this to be more like OSX where any > > "empty" chrome is a draggable point. Think a Preferences dialog. It's full of > > empty chrome. > > Windows are already draggable everywhere, if you are willing to hit the Super > key. Sure, but I guess the original purpose of window-draggable was to use the nice big targets of toolbar and menubar as if they were the titlebar of the window. Tabs are usually below the toolbar and also expose a big blank area when there are not enough tabs. It would make sense to also give this "connected" utility to this area, just as the menu and toolbar have.
sure, not disagreeing with that.
Comment on attachment 210760 [details] [review] WIP: make GtkNotebook window-draggable Marking as needs-work as per comment #1
Not really a blocker
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue for it.