This design seems obviously hideously flawed. The last thing I as a user want is for my pages to start doing a ton of work as I switch away from them. Yet this

This design seems obviously hideously flawed. The last thing I as a user want is for my pages to start doing a ton of work as I switch away from them. Yet this article discusses at length how the only for-sure chance pages get to save state is visibilitychange , as the user tabs away. My computing resources should be spent loading a new page & ensuring maximum responsiveness for further interaction & processing on the new page. There's some.chamce perhaps the visibilitychange event could be delayed, but that seems like a second downside, a need arising from an inherently not-great design. Im surprised such obvious conflict in the design got through the various standards bodies.