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+ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1671424 Title: qtmir destroys windows after requesting them to close Status in Canonical System Image: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
