Re: [w3ctag/design-reviews] Prefetch request changes to improve privacy (#398)

TLDR: I don't think this is ready for a deep review by the TAG, I just wanted to file this issue very early while Chrome and other vendors get their stance straight and proposing ideas in case TAG had any early input.

---

> Is there any explainer in plan to get a better idea what's being done here? (maybe this document if of help).

Ah, yes I actually wrote that document. No explainer yet, as the ultimate direction is not entirely clear yet (sorry).

> Any view on finalising the pulls referenced above?

RE spec: I'll defer to @yoavweiss, as he is currently authoring the spec changes relevant here. But as Anne mentioned, I agree a lot of that is blocked on how implementations decide to move forward.

To be clear: I think we'll likely not have any progress on this until after TPAC when vendors discuss this a bit more, so feel free to defer seriously at this looking until a meeting after 2019-09-04 (when the current label suggests this will be looked at closer). Just wanted to file an issue at  the same time as I wrote Chromium's Intent-to-Implement to get his out earlier rather than later.

> Are you filling a security/privacy questionnaire?

I will, however this won't be done until the direction is more clear (see above).

> Might be useful context [...]

Ah, yes I wrote that too :)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/398#issuecomment-525297860