#931: Speculation rules: target_hint field

Visit on Github.

Opened Feb 13, 2024

こんにちは TAG-さん!

I'm requesting a TAG review of target_hint field for speculation rules prerendering.

This extends speculation rules syntax to allow developers to specify the target_hint field.

This field provides a hint to indicate a target navigable where a prerendered page will eventually be activated. For example, when _blank is specified as a hint, a prerendered page can be activated for a navigable opened by window.open(). The field has no effect on prefetching.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • Relevant time constraints or deadlines: We hope to start an origin trial with partners as soon as possible, so the sooner, the better.
  • The group where the work on this specification is currently being done: WICG
  • The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WHATWG
  • Major unresolved issues with or opposition to this specification: n/a
  • This work is being funded by: Google

You should also know that...

n/a

We'd prefer the TAG provide feedback as (please delete all but the desired option):

☂️ open a single issue in our GitHub repo for the entire review

Discussions

2024-05-20

Minutes

adding assignments

Matthew: it says "for implementation reasons" and also "we want to get rid of this in future" - so how many people are going to use it given that they want to get rid of it and what does that mean for the dev tools. When we've looked at others of these we've wanted a bit more detail on when and how it's gonna be deprecated.

Dan: links to a fragment of speculation rules explainer but no specific user needs..

Dan: adds comment and Matthew will add another comment about deprecation.

also we assign Tess as another reviewer

2024-08-19

Minutes

Amy: no response to our requests for more info in the explainer

Peter: I'll ask for updates

2024-09-09

Minutes

Tess: looks like ... jeffrey asked some questions ... could mark as pending ex feedback?

Jeffrey: I'm assuming they will say it's gonna take a year... Totally possible it will be a constraint for webkit and mozilla also ... only concern I saw is maybe this shows that mozilla is right ... to use anchor tags...

Tess: I think micro-syntax ... knee-jerk reaction is .. we won't need it.

Jeffrey: moz's approach is to design a different micro-syntax... Not obviously better. The comment might be 'please keep working with moz to see what the right syntax is'.

Tess: that would work for me. We could close it now...

Jeffrey: this is a real small tweak to bigger pre-rendering issue.

Tess: this has arch implications because it's redundantly specifying...

<blockquote>

Please keep working with Mozilla to figure out the right syntax for this, especially whether the need for target information reinforces their preference to re-use <a> elements. Beyond that, we don't see any architectural issues and (ignoring any worries about the underlying feature) are satisfied with this extension.

</blockquote>

We agree to close.