4 ms·
> There's no way that the browser could possibly recreate that state by going forward. Of course there is—just don't delete anything immediately. All your stat
by __david__ 10y ago
> There's no way that the browser could possibly recreate that state by going forward.
Of course there is—just don't delete anything immediately. All your state stays there like it's in its own (hidden) tab and gets lazily garbage collected "some time" later. If the user navigates back, there's nothing to rebuild as everything is still sitting there intact.
- chc 10y agoWhile that would work, this seems like the path to "Firefox is too heavy and uses lots of memory."
- mstade 10y agoI don't know how Safari does it, but it works, is incredibly fast, and eats much less memory than Chrome. (My browsing habits suggest Safari is about 30-40% cheaper in terms of memory, but that's anecdata so truck loads of salt required.) In any event, there are way too many replies to keep count of in this thread, but all I can say is that however Safari does it – it just works(tm). Accidental backspace has literally never been an issue for me since they implemented this. There are convincing arguments why backspace as a short cut is a bad idea to begin with, but old habits die hard, and I for one am very happy that Safari makes this work.
- joelwilliamson 10y agoPeople would quickly come to depend on their data not being lost when they leave a page, and then be very unhappy when sometimes it is lost.
- brandon 10y agoWhat do you do about WebSocket connections or hanging GETs? Do you lie to the page about whether its still being rendered visibly? Etc etc. This all seems terribly expensive relative to removing a hotkey used by fewer than 1% of users.