Re: My question about client hints

It seems that the JS+cookie approach wouldn't work well for client hints
that might change in between accesses.
Resources that are sent up to the point JS can run and update its
understanding of a client's preferences will be inadequate in various ways.

In particular, this seems concerning for the save-data hint as it might be:

   - OFF initially because the user was on WiFi, or in their home country
   - ON for a subsequent navigation because the user is now on their mobile
   connection, or roaming abroad.

resulting in less than ideal bandwidth usage.

On Tue, Mar 20, 2018 at 5:33 PM Eric Rescorla <ekr@rtfm.com> wrote:

> At today's session I asked the following question:
>
> Given that you can only send client hints if the site could run JS and set
> a cookie, then
> why can't the site just run JS on first contact, extract this data, and
> store it in a cookie,
> at which point it is available on all previous contacts.
>
> As far as I can tell, the only difference here is on first contact. What
> am I missing.
>
> -Ekr
>
>