Comment 7 for bug 616447
Revision history for this message
| David Barth (dbarth) wrote Re: Quit does not actually quit applications | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It's not as simple as sending a kill to the associated process. Sometimes we do have a direct mapping between a window or a set of windows, and an associated PID. But sometimes not: chromium is such a case where chrome windows, tabs and renderers processes are grouped totally differently. And sometimes there are service processes with no windows anymore, and.
The scope of design for the launcher excluded the case of service applications, and as part of that we have implemented the best solution to the problem we could design: closing windows to reuse a known code paths in applications, ie reproducing what users do with the close buttons.
Introducing a change to send a close signal at this stage is very dangerous: it can work on simple cases, where the xid - pid mapping is simple and known. It will break for the non trivial cases, and we can't be sure of the ramifications of this change in just 1 week of testing (for a 0day-SRU).
An SRU could be provided later after the release, but then it will require a serious exception to the SRU definition, as it will introduce a change in the behavior of the product.