6 ms·
https://www.w3schools.com/jsref/event_onbeforeunload.asp https://www.w3schools.com/jsref/event_onbeforeunload.asp
by rvr_ 4y ago
https://www.w3schools.com/jsref/event_onbeforeunload.asp https://www.w3schools.com/jsref/event_onbeforeunload.asp
- smhg 4y agoI'm baffled any half decent site would use that. I expected some kind of new web/Chrome API. That's a very "bold" choice of 538 if you ask me.
- usmannk 4y agoIt’s not that, they’re pushing the “before you go” page to the history stack. https://developer.mozilla.org/en-US/docs/Web/API/History/pushState https://developer.mozilla.org/en-US/docs/Web/API/History/pus... You can see it if you right click the back button after navigating to the article.
- graderjs 4y agoNo, it wouldn't be that. That can only prevent unload if it throws a native modal up (cousin of alert, confirm, prompt, etc). I think what they must have done is push some URL to the history state, using the History API, to fuck with the back and forward buttons, enabling them to intercept when you navigate back, by having added an additional page in there, that you never visited, but that they can use to serve you this interstitial. Just my 2c