ngraham added a comment.
In D27077#604428 <https://phabricator.kde.org/D27077#604428>, @cfeck wrote: > But the timeout isn't used to give apps more time needed to clean up before they confirm the session can be closed? If I understand it correctly, there should be two timeouts? I don't think so. It doesn't look like apps get the signal to quit until after you actually choose an option in the dialog, or the timeout runs out. Conceptually speaking, having any kind of timeout on a dialog meant to confirm destructive actions is a bad idea. You want the default to be to do nothing, not "do the destructive thing in n seconds". So maybe this isn't actually a destructive action at all. After all, an app with unsaved changes or active processed will block the logout/shutdown absent user interaction. Windows no longer even uses a "confirm logout" dialog anymore AFAIK. However macOS does, with a 60-second timeout. If I think about it a bit more, what makes sense to me is to never show the logout screen in response to a user-initiated action to choose a specific action (e.g. choose log out, shut down, etc from Kickoff). In this case, the user already knows what they want to happen and asking them to confirm is just annoying. However, when pressing the power button, the multi-option screen should be shown by default, with no timeout at all so you need to deliberately choose an option. Does that make sense to anyone else? REPOSITORY R120 Plasma Workspace REVISION DETAIL https://phabricator.kde.org/D27077 To: ngraham, #vdg, #plasma Cc: cfeck, davidedmundson, plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart
