[bumped to next week

• Breakout Rollup
• Issue Triage

Amy: i had a look - and had some questions. Main thing: how it relates to resource hints. Seems to be an alternative to resource hints. Seems to be an old spec that is in CR... .. there's an issue in design reviews - https://github.com/w3ctag/design-reviews/issues/398 Supposed to be a privacy-respectint alternative to resource hints... but may be history that I'm not aware of...

Amy: some replies that I still need to read. [bumped to plenary]

Ran out of time.

Close: managed device, module serviceworker, web codec... PostTask was closed.

Thanks @jeremyroman and @domfarolino for your helpful responses to my questions.

We can see you've thought about various privacy and security implications, but the spec so far doesn't have Privacy or Security Considerations sections, so don't forget to add those.

We're still a little concerned about complexity for authors given the overlap with Resource Hints. We noticed that your ultimate target for this spec is WHATWG, but Resource Hints is going through the Web Performance WG. If you haven't already, it would be worth syncing with them and perhaps considering that as a venue for this work in future.

Besides that, as this was an early review, we are content to close this and wish you luck with the continued incubation of this spec in WICG. We look forward to reviewing again at a later stage.

Amy: it's basically fine but there are some issues before we close it. One thing - relationship with resource hints - that this spec is a superset of that. Which strikes me as odd. They put future venue as whatwg - I put in the comment that they should sync with web performance wg and consider that as a venue. Other thing I thought about - somethings about the prerender it's gonna need. Changes to javascript - for analytics- will need to know if it's a pre-render. They've said 'so the browser can use heuristics' but no detail on heuristics. Implementation detail - might not reveal to the user what heuristics are.

Dan: Privacy issue?

Amy: they have good answers on to the privacy & security questionnaire on that.

Dan: so maybe we can close?

Dan: if it's a superset then why do we need the thing that's supsersetted? Feels like there should definitely be some discussion with web perf wg.

Amy: initially asked why they can't extend Resource Hints, and they said the way that works makes it difficult to extend because of link headers and stuff

Dan: suggest you paste your comment, mark as proposed close and close at the plenary.