Unload was designed to fire when the document is being unloaded. Our goal is to use this soft deprecation to inform the timeline for the last phase ( hard deprecation of unload) in which these opt-outs will be removed or reduced. Note that we also offer a menu of opt-out options in case this soft deprecation timeline doesn't provide sufficient time to migrate away from unload. In addition, from Q3 2024, we intend to start a generic phase where unload will gradually cease to function on any sites, starting with 1% of users and ending with 100% of users by the end of Q1 2025. Ending with 100% of users by the end of Q3 2024.Starting with 1% of users from Chrome 120 (end of November 2023).A scoped phase where unload will gradually cease to function for the top 50 popular sites ( reference as of the time of writing).Local testing by enabling a flag in Chrome 117 (September 2023)įollowing these outreach and trial phases, here is how we expect the soft deprecation to roll out:.In the wild testing via the Permission-Policy API for unload in Chrome 115 (July 2023).To complement this outreach, we also started to offer ways to test the effect of deprecating unload from Chrome 115: In parallel to the implementation work, we conducted a large outreach which resulted in a significant drop of unload usage. We noted that unload behavior would likely be subject to changes as early as January 2019, when we announced our intent to implement a back/forward cache. Deprecation timeline Update: This timeline has been updated as of 13th November 2023. The unload event will be gradually deprecated by gradually changing the default so that unload handlers stop firing on pages unless a page explicitly opts in to re-enable them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |