Re: [blink-dev] Re: Intent to Continue Experimenting: Speculation Rules (Prefetch)

[Jeremy Roman]

Hopefully around the end of Q1.

On Mon, Jan 31, 2022 at 12:48 PM Joe Medley  wrote:

> Jeremy,
>
> When do you hope to ship this?
>
> Joe
> Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com |
>  816-678-7195
> *If an API's not documented it doesn't exist.*
>
>
> On Fri, Jan 28, 2022 at 11:51 AM Jeremy Roman 
> wrote:
>
>> On Fri, Jan 28, 2022 at 4:33 AM Yoav Weiss 
>> wrote:
>>
>>> LGTM to continue experimentation. Note that this would bring the OT to
>>> 11 milestones, which is approaching the limits of OT timelines.
>>>
>>> On Wed, Jan 26, 2022 at 9:57 PM Jeremy Roman 
>>> wrote:
>>>
 On Wed, Jan 26, 2022 at 10:18 AM Yoav Weiss 
 wrote:

> Any current feedback from the OT up until now?
>

 Feedback on the speculation rules API itself has been relatively
 limited. We had one issue where server postprocessing incorrectly
 interpreted a 

Re: [blink-dev] Re: Intent to Continue Experimenting: Speculation Rules (Prefetch)

['Joe Medley' via blink-dev]

Jeremy,

When do you hope to ship this?

Joe
Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com |
 816-678-7195
*If an API's not documented it doesn't exist.*


On Fri, Jan 28, 2022 at 11:51 AM Jeremy Roman  wrote:

> On Fri, Jan 28, 2022 at 4:33 AM Yoav Weiss  wrote:
>
>> LGTM to continue experimentation. Note that this would bring the OT to 11
>> milestones, which is approaching the limits of OT timelines.
>>
>> On Wed, Jan 26, 2022 at 9:57 PM Jeremy Roman 
>> wrote:
>>
>>> On Wed, Jan 26, 2022 at 10:18 AM Yoav Weiss 
>>> wrote:
>>>
 Any current feedback from the OT up until now?

>>>
>>> Feedback on the speculation rules API itself has been relatively
>>> limited. We had one issue where server postprocessing incorrectly
>>> interpreted a 

[blink-dev] Re: Intent to Continue Experimenting: Speculation Rules (Prefetch)

[Jeremy Roman]

On Fri, Jan 28, 2022 at 4:33 AM Yoav Weiss  wrote:

> LGTM to continue experimentation. Note that this would bring the OT to 11
> milestones, which is approaching the limits of OT timelines.
>
> On Wed, Jan 26, 2022 at 9:57 PM Jeremy Roman  wrote:
>
>> On Wed, Jan 26, 2022 at 10:18 AM Yoav Weiss 
>> wrote:
>>
>>> Any current feedback from the OT up until now?
>>>
>>
>> Feedback on the speculation rules API itself has been relatively limited.
>> We had one issue where server postprocessing incorrectly interpreted a
>> 

[blink-dev] Re: Intent to Continue Experimenting: Speculation Rules (Prefetch)

[Yoav Weiss]

LGTM to continue experimentation. Note that this would bring the OT to 11
milestones, which is approaching the limits of OT timelines.

On Wed, Jan 26, 2022 at 9:57 PM Jeremy Roman  wrote:

> On Wed, Jan 26, 2022 at 10:18 AM Yoav Weiss 
> wrote:
>
>> Any current feedback from the OT up until now?
>>
>
> Feedback on the speculation rules API itself has been relatively limited.
> We had one issue where server postprocessing incorrectly interpreted a
> 

[blink-dev] Re: Intent to Continue Experimenting: Speculation Rules (Prefetch)

[Jeremy Roman]

On Wed, Jan 26, 2022 at 10:18 AM Yoav Weiss  wrote:

> Any current feedback from the OT up until now?
>

Feedback on the speculation rules API itself has been relatively limited.
We had one issue where server postprocessing incorrectly interpreted a

[blink-dev] Re: Intent to Continue Experimenting: Speculation Rules (Prefetch)

[Yoav Weiss]

Any current feedback from the OT up until now?

On Monday, January 24, 2022 at 4:58:16 PM UTC+1 Jeremy Roman wrote:

> Contact emails
>
> jbro...@chromium.org, kenjibah...@chromium.org
>
> Explainer
>
> https://github.com/WICG/nav-speculation/blob/main/triggers.md
>
> Specification
>
> https://wicg.github.io/nav-speculation/speculation-rules.html
>
> https://wicg.github.io/nav-speculation/prefetch.html
>
> Summary
>
> Speculation Rules is a flexible syntax for defining what outgoing links 
> are eligible to be prepared speculatively before navigation. It enables 
> access to additional enhancements, such as use of a private prefetch proxy, 
> where applicable.
>
> Participants in this trial can use this syntax to request prefetching of 
> links they expect the user is likely to visit next.
>
> This is a request to extend the previous experiment 
> .
>  
> We would like to extend the experiment for milestones M98 to M101 
> (inclusive), in order to continue to gather data as a partner makes 
> improvements to their integration and to shave some of the rough edges off 
> the feature. There is an ongoing early access program 
> 
>  
> to allow more publishers to receive IP anonymized traffic as we refine this.
>
> We now support "prefetch" rules and intend to deprecate 
> "prefetch_with_subresources" (at least for now) during this extension. 
> Cross-origin uncredentialed prefetch without IP anonymization is now 
> supported.
>

That's a new addition of this extension, right?
 

> Users can now enable access to IP anonymization from any origin through a 
> Chrome setting.
>

Is this setting applicable to all sites? Just prefetched ones? 
 

>
> Internal analysis from the current experiment with significant improvement 
> to the largest contentful paint time when successful. Though prefetching 
> with subresources (NoStatePrefetch) provides some additional improvement, 
> it incurs over a much higher byte cost on average. We believe that in most 
> cases prefetching more possible outgoing navigation is typically a better 
> tradeoff than also prefetching subresources, so we are focusing on shipping 
> prefetch of the main resource. Many outbound navigations are currently 
> ineligible due to cookies existing on the destination site, which motivates 
> future improvements to allow sites to participate in uncredentialed 
> prefetch through an additional opt-in. (I've requested clearance to release 
> approximate numbers, but that hasn't been approved at this point.)
>
> Blink component
>
> Internals>Preload 
> 
>
> TAG review
>
> https://github.com/w3ctag/design-reviews/issues/611
>
> TAG review status
>
> Complete (recommended followup review TBA)
>
> Risks
>
> Interoperability and Compatibility
>
> Gecko: No signal
>
> WebKit: No signal
>
> Web developers: Past success with  
>  and libraries like QuickLink, and 
> discussion with some partners suggests interest in this space.
>
>
> Goals for experimentation
>
> To gather feedback about the convenience of the Speculation Rules syntax, 
> and to gather data about performance improvements for navigations that are 
> prefetched, directly and via a private prefetch proxy (subject to the 
> limitations mentioned above).
>
> Ongoing technical constraints
>
> No significant technical constraints anticipated.
>
> Will this feature be supported on all six Blink platforms (Windows, Mac, 
> Linux, Chrome OS, Android, and Android WebView)?
>
> Chrome for Android (non-WebView) only, at present.
>
> Eventually other platforms will be supported.
>
> Is this feature fully tested by web-platform-tests 
> 
> ?
>
> Not yet, but we have plans to 
> 
> .
>
> Flag name
>
> The origin trial feature name will continue to be SpeculationRulesPrefetch.
>
> Tracking bug
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1173646
>
> Link to entry on the Chrome Platform Status
>
> https://chromestatus.com/feature/5740655424831488
>
> Links to previous Intent discussions
>
> Intent to prototype: 
> https://groups.google.com/a/chromium.org/g/blink-dev/c/1q7Fp3zpjgQ
>
> Intent to experiment: 
> https://groups.google.com/a/chromium.org/g/blink-dev/c/Cw-hOjT47qI/m/CY7qVZP5AQAJ
>
> Intent to continue experimenting: 
> https://groups.google.com/a/chromium.org/g/blink-dev/c/T3nKEipKv-4/m/rKJ0uFR3BAAJ
>
>

-- 
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+unsubscr...@chromium.org.
To view thi