| 1 | | Coincidentally, I've been looking into removing use of the `unload` event (#55491) because Chrome intends to [https://developer.chrome.com/blog/deprecating-unload/ deprecate it], and more importantly because [https://web.dev/bfcache/#never-use-the-unload-event it prevents bfcache]. But something else that blocks bfcache is `Cache-Control: no-store`, which this ticket is all about. Adding `no-store` wouldn't have caused any performance regression in the admin in 6.3 because `wp-heartbeat` uses the `unload` event. However, with this removed, the introduction of `no-store` holds back the performance of page navigations in the admin ''and'' the frontend by disabling bfcache. POC plugin: https://gist.github.com/westonruter/8c19d87a80a36e8f24db910750162628 |
| | 1 | Coincidentally, I've been looking into removing use of the `unload` event (#55491) because Chrome intends to [https://developer.chrome.com/blog/deprecating-unload/ deprecate it], and more importantly because [https://web.dev/bfcache/#never-use-the-unload-event it prevents bfcache]. But something else that blocks bfcache is `Cache-Control: no-store`, which this ticket is all about. Adding `no-store` wouldn't have caused any performance regression in the admin in 6.3 because `wp-heartbeat` uses the `unload` event. However, with this removed, the introduction of `no-store` holds back the performance of page navigations in the admin ''and'' the frontend by disabling bfcache. |