qtmir destroys windows after requesting them to close

[Albert Astals Cid]

Using unity7:
 * Open kate
 * write something very important in the text area
 * Press Alt+F4 because you're not very smart
 * Get dialog saying you have unsaved changes
 * You can:
   * save (which ends in a quit after saving)
   * cancel the close

Using unity8
 * Open kate
 * write something very important in the text area
 * Press Alt+F4 because you're not very smart
 * You lost your very important text

[Michał Sawicz (saviq)]

Part of the answer is "that's bad design, kate should store the state and restore it later".

But we will support this kind of behaviour anyway. Need to let the application reply "no" to the close request. We'll still need a "force quit" for misbehaving apps.

[Daniel van Vugt (vanvugt)]

The test case with kate works correctly in mir_proving_server (Alt+F4 brings up a Save Documents dialog). It's only failing in Unity8.

And gedit apparently has the same Alt+F4 bug under Mir demo servers so GTK may need fixing too.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

See also bug 1672751

[Daniel d'Andrada (dandrader)]

qtmir always destroys a window if it doesn't do so itself after being requested to close.

Specially on desktop, requesting a window to close doesn't necessarily mean it should destroy itself. It's a common idiom for an application to just hide it instead, so it can be reused next time it's needed (particularly for child windows).

Some might even stay around and just popup a dialog if there's modified content that hasn't been saved yet.

So on desktop we should just send the close request without further expectations. On phone though, we should keep the current behavior of forcibly destroying the window if it doesn't comply after some time.

I wouldn't mix this bug with gtk+

[Daniel van Vugt (vanvugt)]

Indeed the close button and Alt+F4 should never ever destroy a window.

They should just send the window an event: mir_event_type_close_window
Then it's up to the app how to proceed.