> I don't remember exact stats, but it ended up being pretty reliable across > browsers for our needs in disconnecting on a window close - the rare > instance of it not working just had them online for a bit before timing out. > > > Ah, okay, so this really just uses brute force to ensure that the connection is disconnected; gracefully if possible, timeout if not? Works for that use case, not so much for trying to send a last pause request and accurately capture state to resume in the next page.
Also, just an update: I tried adding a flag in my library, isPausing, and setting it to true when pause is called. Then any new request while isPausing is true is synchronous, but that resulted in getting stuck on the unresponsive page for 60 seconds. Out of curiosity, was browser unload the use case in mind when pause support was added to the spec?
