Moving popup windows drags the application's main window behind it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
New
|
Unknown
|
|||
gnome-shell (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is.
For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to.
Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it.
Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together.
In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows.
It's pure madness.
I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design.
Why?
What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable??
Here's a very real-life example:
As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving.
Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window.
The everyday examples are countless.
This is idiotic. Seriously, what are you doing?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.3.0-62-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019
GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
.tmp.unity_
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckR
CompizPlugins: No value set for `/apps/
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 12 18:11:28 2020
DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit()
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia-340, 340.108: added
ExtraDebuggingI
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647]
NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/
Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (2465 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.family: Type1Family
dmi.product.name: Aspire V3-571G
dmi.product.sku: Aspire V3-_0648_V2.07
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.14.
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Sun Jul 12 15:12:31 2020
xserver.configfile: default
xserver.errors:
modeset(G0): eglGetDisplay() failed
modeset(G0): glamor initialization failed
NVIDIA(0): Failed to initiate mode change.
NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.
Changed in gnome-shell (Ubuntu): | |
status: | Won't Fix → Opinion |
status: | Opinion → Won't Fix |
Changed in gnome-shell: | |
status: | Unknown → New |
This is a feature we inherited from GNOME. It is not a design choice by Ubuntu.
To disable it just set:
Gnome Tweaks > Windows > Attach Modal Dialogs = OFF