Braw mornin' TAG!

I'm requesting a TAG review of Priority Hints.

API and markup that will provide developers with the control to indicate a resource's relative importance to the browser for the browser to use when making loading prioritization decisions.

• Explainer¹ (minimally containing user needs and example code): https://github.com/WICG/priority-hints/blob/main/EXPLAINER.md
• Specification URL: https://wicg.github.io/priority-hints/
• Tests: priority-hints folder of WPT
• Security and Privacy self-review²: https://wicg.github.io/priority-hints/#security_privacy
• GitHub repo (if you prefer feedback filed there): https://github.com/WICG/priority-hints
• Primary contacts (and their relationship to the specification):
  • Patrick Meenan (pmeenan), Google, Author
  • Yoav Weiss (yoavweiss), Google, W3C web performance working group chair
• Organization(s)/project(s) driving the specification: Google
• Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/WICG/priority-hints/issues
• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5273474901737472

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: None (though it is currently in origin trial and it would be nice to transition sites to a finalized solution without interruption).
• The group where the work on this specification is currently being done: W3C Web Performance Working Group
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WICG
• Major unresolved issues with or opposition to this specification: None (though "importance" as the attribute name gets a lot of active discussion).
• This work is being funded by: Google

You should also know that...

There was initial work done in 2018 with an initial review in #241 but the work went stale at the time. The revised spec limits the priority hints to the fetch of the resource directly referenced by the markup/API and doesn't cascade to frame children or script downstream fetches. That was a particularly controversial issue with the initial spec that also didn't have a clear use case and has since been removed.

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

🐛 open issues in our GitHub repo for each point of feedback