We would like to extend the origin trial for 3 additional milestones, with the extension starting in 110 continuing through 112. The initial experiment was approved for the OT running from 107 through 109.
This feature allows pages to disable the running of unload event handlers. The goal is to :
- allow sites that have removed all unload handlers to ensure they do not accidentally add new ones
- allow sites to remove unload handlers when updating the code is infeasible
Unload event handlers are problematic for various reasons and prevent use of BFCache on Desktop (see https://web.dev/bfcache/#never-use-the-unload-event).
Validate that this allows sites using it to improve their BFCache hit rate
We had requested this Origin Trial to be run for 3 milestones, specifically from 107 to 109 without realizing the Origin Trial guideline suggesting 6 milestones. We would like to extend this OT for another 3 milestones or to 112 inclusive by applying the 6 milestone guidelines we originally missed, to give sufficient time for partners to give us feedback.
Ongoing technical constraints
When this header is present, attempts to add an unload event handler will result in an error on the console (just as would happen for any other Permissions Policy violation).
or via Origin Trial Token
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/ryjRQsxyo2Y/m/xOPh6glQBAAJ
Ready for Trial: https://groups.google.com/a/chromium.org/g/blink-dev/c/38Dpu-uhwFcIntent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/RhzscAx3qc8/m/qgBkBFmzAgAJ?utm_medium=email&utm_source=footer
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA5e69_hiyb60B9h6d88ccuoDavYnqDg89LUkgcG6iozfD8e0w%40mail.gmail.com.