You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This proposal allow developers to specify a tag field in their speculation rules. This is used to compose a Sec-Speculation-Tags header, which is sent along with same-site prefetch and prerender requests.
The main use case is allowing the server to know which of several parties (e.g. individual page developer, framework, CMS, or CDN) is responsible for a given speculative load.
Request for Mozilla Position on an Emerging Web Specification
I was unsure whether it's worth asking for a position on specific new additions to the speculation rules syntax, which was judged holistically in #620 as neutral.
I erred on the side of asking for more input, but, please let me know if there's a preferred path for future such additions.
The text was updated successfully, but these errors were encountered:
This proposal allow developers to specify a
tag
field in their speculation rules. This is used to compose aSec-Speculation-Tags
header, which is sent along with same-site prefetch and prerender requests.The main use case is allowing the server to know which of several parties (e.g. individual page developer, framework, CMS, or CDN) is responsible for a given speculative load.
Request for Mozilla Position on an Emerging Web Specification
@
-mention GitHub accounts): @domenicOther information
I was unsure whether it's worth asking for a position on specific new additions to the speculation rules syntax, which was judged holistically in #620 as neutral.
I erred on the side of asking for more input, but, please let me know if there's a preferred path for future such additions.
The text was updated successfully, but these errors were encountered: