Re: [w3ctag/design-reviews] Migrating some high-entropy HTTP request headers to Client Hints. (#320)

@chaffeqa: It's a bit tangential to this specific review request, which I'd like to keep focused on the two hints I'd like to add. Still, I think I agree that viewport information can be useful for content negotiation (and Chrome actually already ships a [`Viewport-Width`](https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-06#section-3.3) hint that you can persistently opt-into via [`Accept-CH-Lifetime`](https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-06#section-2.2.2)!). But I think I disagree that it's not a fingerprinting concern to always pass on hints, generally. An explicit opt-in seems like the right compromise to me.

-- 
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/320#issuecomment-456359983