Unexpected behavior of OS X client's close button

[pgambling]

The close button currently shuts down the application. However, the normal behavior of OS X's close button is to close the window while the application remains active in the dock. Closing the application is accomplished by cmd+q or app menu->quit.

[shaunlebron]

There are some applications that explicitly close after its last window is closed (e.g. Popcorn Time, System Preferences). Regardless of that, if the window is closed, there's not much else the user can do since our menu only has default items inherited from Atom Shell.

[pgambling]

Wouldn't you still see the dock bounce and notifications even when the window is closed?

On Tue, Feb 17, 2015, 9:51 AM Shaun LeBron notifications@github.com wrote:

Closed #97 https://github.com/oakmac/cuttle/issues/97.

— Reply to this email directly or view it on GitHub https://github.com/oakmac/cuttle/issues/97#event-237012451.

[shaunlebron]

Not currently. @oakmac, should we re-open the window if the dock icon is clicked?

[pgambling]

I mean IF Cuttle only closed the window and not the application when clicking close, I'd still expect the dock icon the bounce and growl notifications to appear.

[oakmac]

I don't know enough about Mac common defaults to have an informed opinion here.

As a general heuristic, I think we should support the Principle of least astonishment ;)

[CASandmann]

In my admittedly limited interactions with OSX, most applications seem to work the way Phil described:

• If a user closes the application window, the task remains active (the blue light still shows under the icon on the dock)
• If a notification occurs while the window is closed, the icon will bounce in the tray
• If the user then clicks the icon, the window reopens
• Mac users know they can definitively close applications by right-clicking the dock icon and selecting exit