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 722839 - dragging GtkFileChooserDialog modal should not drag parent window
dragging GtkFileChooserDialog modal should not drag parent window
Status: RESOLVED DUPLICATE of bug 697680
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-01-23 15:42 UTC by Derek Moore
Modified: 2015-03-05 10:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Derek Moore 2014-01-23 15:42:21 UTC
It is frequent that a user wants to look at the contents of a parent window when engaging in Open or Save operations.

It is generally not expected that underlying contents will move along with the overlaying dialog when moving them out of the way to inspect underlying contents, making inspection of the underlying contents impossible.

This behaviour confuses the user and forces the user to close the dialog, losing any filesystem navigation or file naming work that they have already done.

A user should be able to move the Open/Save dialog out of the way to inspect the contents of the parent window so they can confirm the actions they are about to engage in.
Comment 1 Emmanuele Bassi (:ebassi) 2014-01-23 16:06:49 UTC
GTK+ is not responsible for this behaviour: the window manager (in this case: Mutter/GNOME Shell) is.

incidentally, there's a user setting to tell Mutter not to attach modal dialogs to their parent:

  gsettings set org.gnome.mutter attach-modal-dialogs false

re-assigning.
Comment 2 Florian Müllner 2015-03-05 10:08:15 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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