Yes, my concern is that status quo for several/many applications is that they do no connect to saveStateRequest() or commitDataRequest() and *only* perform interaction on window close events (since this is the regular case *during* the session)
Stripping this mechanism will cause a behavioral change that is prone to cause data loss on session exit - thus such change may be denied upstream. If so, the status quo can be restored by sending close events w/o causing
a) the actual loss of windows in the running session
b) the application to "accidentally" quit early
I don't discuss "what should be", but "what mess have we caused and how do we get around that" ;-)
Yes, my concern is that status quo for several/many applications is that they do no connect to saveStateRequest() or commitDataRequest() and *only* perform interaction on window close events (since this is the regular case *during* the session)
Stripping this mechanism will cause a behavioral change that is prone to cause data loss on session exit - thus such change may be denied upstream. If so, the status quo can be restored by sending close events w/o causing
a) the actual loss of windows in the running session
b) the application to "accidentally" quit early
I don't discuss "what should be", but "what mess have we caused and how do we get around that" ;-)