Link to Intent To Experiment:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/ONn6qsdwHUo/zHqyNL46BQAJ
Contact emails
nbu...@chromium.org, bo...@chromium.org
Summary
The purpose of ForceLoadAtTop is to provide an opt-out for Scroll To Text for privacy sensitive sites, as discussed in WICG/ScrollToTextFragment#80. The ForceLoadAtTop feature allows sites to indicate that they should be loaded at the top of the page, and not perform any scroll on load, including element fragment identifiers, scroll restoration, and Scroll To Text. See link at top for full original summary.
This policy was meant as a DocumentPolicy but was offered as an independent origin-trial until DocumentPolicy was ready. In the original intent we set the timeline to 83-84 as DocumentPolicy was expected to be available, at least via origin trial, in M85. That's since been pushed back (expecting an origin trial in M86) so we'd like to extend this trial to provide continuity until DocumentPolicy is available.
Experimental timeline
M83 - M85 (Extended from M83 - M84)
<Content below copied from original intent>
Link to “Intent to Prototype” blink-dev discussion
Goals for experimentation
We expect usage to be pretty low, and won't provide much insight as this is simply an opt-out.
Any risks when the experiment finishes?
Sites that wish to continue using the ForceLoadAtTop feature will have to add the HTTP header: "Document-Policy: force-load-at-top".
Ongoing technical constraints
None.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Yes.
Link to entry on the feature dashboard
--
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/CANMmsAvO8evi1Q5cyNSm%3Dd47p9ZFYvVM%2Bmgb2DL9qM4q_jaQTg%40mail.gmail.com.