4 ms·
Chrome might not be able to, but the website can, surely? Why not leave it to developers to properly handle state within their application (e.g. by using histor
by another-dave 10y ago
Chrome might not be able to, but the website can, surely? Why not leave it to developers to properly handle state within their application (e.g. by using history and 'beforeunload' functionality) rather than second-guessing it at a browser level?
- DonHopkins 10y agoThen the problem would ALREADY be solved, because all developers would already be properly handling state within their application instead of second-guessing it at a browser level. But they don't.