4 ms·

That's a MacOS thing, not just a Safari thing. Windows stay open until you close them, even across restarts. MacOS, like iOS, has mostly retired the concept of

by abalone 10y ago

That's a MacOS thing, not just a Safari thing. Windows stay open until you close them, even across restarts. MacOS, like iOS, has mostly retired the concept of "quitting an app kills state". (You can go back to the old behavior via a system setting: "Close windows when quitting an app")

Nullabillity 10y ago
Storing stuff on disk that should be kept purely in-memory is a Mac thing?
- kalleboo 10y ago
  Being able to pull the plug/battery on a computer and then having the restored state be exactly the same is a Mac thing, yeah.
  - yoz-y 10y ago
    In this particular case though it should not do so. Users do expect the private tabs to disappear after the window closes, no matter how it is closed.
    - Someone 10y ago
      I am not sure reopening private windows is a good idea, either, but Mac OS removed the rule "quitting an application closes its windows". Given that, it is logical that it reopens private windows, just as, for example, TextEdit or Numbers reopen windows with content you never explicitly saved (even across reboots)
  - dTal 10y ago
    >Being able to pull the ... battery on a computer... is a Mac thing Nope!
saurik 10y ago
This feature isn't some kind of evil magic... it isn't like it is serializing the virtual memory state of the entire process to disk in the style of unexec(): programs have to manually decide what they think matters for their suspension state; correspondingly, if this happens, Safari would have to be incorrectly saving information that the user clearly doesn't expect or want.
- abalone 10y ago
  > Safari would have to be incorrectly saving information that the user clearly doesn't expect or want. This is vestigial thinking from the MacOS perspective. The concept of "saving" is gone. The concept of "memory state" versus "disk" is gone, from the user perspective. Those are all implementation details now. For the user it's simply, your windows stay open until you close them. Quitting does not close windows, so it's not unusual to see them when you return to an app. By the way, Safari in iOS does exactly the same thing. And given that iOS kills apps on its own, there would be no question that randomly killing private sessions would be a bug. I mean maybe you could distinguish between a force quit and an OS quit, but why? Just close the windows if you want to clear them. The private window guarantee is there will be no trace after you close the window. It's just vestigial thinking that quitting apps also closes windows.
dTal 10y ago
What is "quitting" then? How much state is stored? Between "no state" (window is a dead bitmap) and "all the state" (program is simply paused) is a lot of wiggle room.

by abalone 10y ago

Nullabillity 10y ago

Storing stuff on disk that should be kept purely in-memory is a Mac thing?

kalleboo 10y ago
Being able to pull the plug/battery on a computer and then having the restored state be exactly the same is a Mac thing, yeah.
- yoz-y 10y ago
  In this particular case though it should not do so. Users do expect the private tabs to disappear after the window closes, no matter how it is closed.
  - Someone 10y ago
    I am not sure reopening private windows is a good idea, either, but Mac OS removed the rule "quitting an application closes its windows". Given that, it is logical that it reopens private windows, just as, for example, TextEdit or Numbers reopen windows with content you never explicitly saved (even across reboots)
- dTal 10y ago
  >Being able to pull the ... battery on a computer... is a Mac thing Nope!

saurik 10y ago

This feature isn't some kind of evil magic... it isn't like it is serializing the virtual memory state of the entire process to disk in the style of unexec(): programs have to manually decide what they think matters for their suspension state; correspondingly, if this happens, Safari would have to be incorrectly saving information that the user clearly doesn't expect or want.

abalone 10y ago
> Safari would have to be incorrectly saving information that the user clearly doesn't expect or want. This is vestigial thinking from the MacOS perspective. The concept of "saving" is gone. The concept of "memory state" versus "disk" is gone, from the user perspective. Those are all implementation details now. For the user it's simply, your windows stay open until you close them. Quitting does not close windows, so it's not unusual to see them when you return to an app. By the way, Safari in iOS does exactly the same thing. And given that iOS kills apps on its own, there would be no question that randomly killing private sessions would be a bug. I mean maybe you could distinguish between a force quit and an OS quit, but why? Just close the windows if you want to clear them. The private window guarantee is there will be no trace after you close the window. It's just vestigial thinking that quitting apps also closes windows.

dTal 10y ago

What is "quitting" then? How much state is stored? Between "no state" (window is a dead bitmap) and "all the state" (program is simply paused) is a lot of wiggle room.