Contact emailsrobert...@chromium.org, dome...@chromium.org

Explainer
https://github.com/WICG/nav-speculation/blob/main/speculation-rules-tags.md

SpecificationNone yet, but we'll be writing one during the prototype phase

Summary

This enables developers to add tag field to speculation rules. This
optional field can be used to track the source of speculation rules, e.g.
to treat them differently at an intermediary server. Any tags associated
with a speculation will be sent with the Sec-Speculation-Tags header.


Blink componentInternals>Preload
<https://issues.chromium.org/issues?q=customfield1222907:%22Internals%3EPreload%22>

Motivation

There may be multiple parties on a single referring page which are setting
up speculation rules, e.g. CDNs, frameworks, or individual pages. It can be
useful for server code to respond differently to speculative navigation
requests, depending on which source triggered them. Today, there is no way
for servers to perform this kind of differentiation. All speculative
navigation requests appear the same to the server. This feature provides
such a mechanism.


Initial public proposalhttps://github.com/WICG/nav-speculation/issues/336

Search tagsspeculationrules
<https://chromestatus.com/features#tags:speculationrules>, prerendering
<https://chromestatus.com/features#tags:prerendering>, prefetch
<https://chromestatus.com/features#tags:prefetch>

TAG reviewhttps://github.com/w3ctag/design-reviews/issues/721 The TAG is
generally dissatisfied with speculation rules, claiming that the syntax is
too complicated. As such, we don't believe asking for review of this
additional feature would be fruitful.

TAG review statusNot applicable

Risks


Interoperability and Compatibility

The entire speculative loading feature is a progressive enhancement, so in
general risks are low in this area.


*Gecko*: No signal (
https://github.com/mozilla/standards-positions/issues/1172) Mozilla is
neutral on speculation rules syntax in general (
https://github.com/mozilla/standards-positions/issues/620), although
positive on prefetching. We opened a new request for this specific feature
to ensure we captured any of their input.

*WebKit*: No signal (https://github.com/WebKit/standards-positions/issues/54)
WebKit has not yet responded to our 2022 request for a position on
speculation rules in general. We have updated the thread to point them to
this latest addition anyway.

*Web developers*: Positive (
https://github.com/WICG/nav-speculation/blob/main/speculation-rules-tags.md#stakeholder-feedback
)

*Other signals*:

Activation

Due to how new fields in speculation rules are interpreted in older
versions of Chrome, using this field on the rule level can cause the rules
to be dropped. A workaround is using it on the ruleset level only during
this transition period.
https://github.com/WICG/nav-speculation/blob/main/speculation-rules-tags.md#location-of-the-tags-within-the-json


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?

None


Debuggability

We would like to use the presence of ruleset-level tags to improve
DevTools's existing display of speculation rules rulesets:
https://issues.chromium.org/issues/393408589


Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
?Not yet, but we plan on doing so during the prototyping phase

Flag name on about://flagsNone

Finch feature nameSpeculationRulesTag

Requires code in //chrome?False

Tracking bughttps://issues.chromium.org/issues/381687257

Estimated milestones

No milestones specified


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6503137340555264?gate=6399349724282880

This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 
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 this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8a%2B4uVDq1V1ZvrkUj9Jg3tbnbnqNXfeHhxZSSMj1mXVg%40mail.gmail.com.

Reply via email to