- From: Daniel Appelquist <notifications@github.com>
- Date: Tue, 19 Jul 2022 01:43:59 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 July 2022 08:44:12 UTC
So we're just discussing in our breakout this morning. And @cynthia has given some further detail and how it fits into bfcache. I was a bit confused by this "Some browsers, like Desktop Chrome and Desktop Firefox, have chosen to keep the unload event reliable, so the existence of unload handlers makes a page ineligible for BFCache, hurting performance. In others like Android Chrome & Android [Firefox](https://groups.google.com/a/mozilla.org/g/dev-platform/c/3pQRLPZnQgQ/m/dsA1w4iiAwAJ), and WebKit-based browsers (Desktop Safari & all iOS browsers), if the page is eligible for BFCache, the unload handlers will not run, further increasing the unreliability of unload handlers." because it sounds like part of the motivation here is to patch a problem with current implementations? Can you clairfy? We're having our f2f meeting next week and we will further discuss there and hopefully be able to close this. Thanks for bearing with us! -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/738#issuecomment-1188772037 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/738/1188772037@github.com>
Received on Tuesday, 19 July 2022 08:44:12 UTC