- From: Jatinder Mann <jmann@microsoft.com>
- Date: Tue, 3 Apr 2012 23:03:22 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: James Graham <jgraham@opera.com>, Ian Hickson <ian@hixie.ch>, "arvind@google.com" <arvind@google.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
> No, some of them are basic user-facing correctness behavior and have nothing to do with CPU usage... Those are the ones where getting it right on unload matters very much, because the worst case is completely incorrect behavior, not just more CPU hogging. Help me understand this one better. What scenarios are you thinking? The main unload scenario for visibilitychange I can think of is saving data before the unload and this is the typical unload event use case. Are there session history specific scenarios that you concerned with? If so, we can make firing visibilitychange during unload tied to if the UA supports session history traversal. > OK, good. Clearly if the hidden state doesn't change when unloading there should be no event. ;) I just wanted to make sure you weren't suggesting changing that behavior. Jatinder
Received on Tuesday, 3 April 2012 23:03:57 UTC