[blink-dev] Intent to Remove: Legacy Client Hint Mode

Fixing the subject prefix, apologies. On Mon, Mar 7, 2022 at 7:54 AM Ari Chivukula wrote: > Contact emails > > aric...@chromium.org, jadekess...@chromium.org, miketa...@chromium.org > > Design Doc > > > https://docs.google.com/document/d/1igtMPtVTiX24bVaUo6tBgx3B16-HmUVPG7iDP5HkzD0/edit > > Spec

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

We've heard back from Cloudflare and Akamai who don't seem to depend on this legacy Android behavior. This change is currently targeted for M104. ~ Ari Chivukula (Their/There/They're) On Fri, Apr 8, 2022 at 8:01 AM Ari Chivukula wrote: > That's a good question! At the moment there isn't a plan

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

Hi API Owners, The goal of this intent is to remove the `legacy mode` behavior of four client hints (device-memory, dpr, width, and viewport-width). This `legacy mode`, only active on Android, auto-delegates client hints to third-party subresources if the first party requests the hint at all. This

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

LGTM1 /Daniel On 2022-05-10 23:32, Ari Chivukula wrote: Hi API Owners, The goal of this intent is to remove the `legacy mode` behavior of four client hints (device-memory, dpr, width, and viewport-width). This `legacy mode`, only active on Android, auto-delegates client hints to third-par

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

LGTM2 While usage going up is concerning, I don't think we could improve our understanding of the risk with any additional metrics, since usage is on the server side. Testing of sites that receive the header is the best we can do,

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

LGTM3 Thanks for following up on this!! On Wed, May 11, 2022 at 5:50 PM Philip Jägenstedt wrote: > LGTM2 > > While usage going up > is > concerning, I don't think we could improve our understanding of the risk > with any additio

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

How can we get a good grip on the web compatibility of this change? The use counters are a high, but as you point out, the number of sites that actually depend on the legacy client hints is lower. The question is just "how much lower?". You listed a number of affected sites. Has anyone checked

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

I haven't had issues loading those sites on Firefox mobile (which doesn't have client hints), but haven't specifically tried loading them on Chrome Android w/o hints enabled. It's true that we're betting on lower dependency given this change only affects Chrome on Android (where the default delegat

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

Speaking on behalf of Cloudinary: - We've started treating the modern hints the same as the legacy hints, server-side - We've identified which customers who are sending us legacy hints and are working on an outreach plan It would be nice to have: - some certainty about the new HTML syntax. Is

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

The modern syntax (I assume you mean third-party delegation of client hints via HTML) is shipping in M100 (stable release at the end of March). There isn't a plan to remove any existing client hint names. The question here is whether any websites are depending on dpr, width, viewport-width, or dev

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

@Eric Portis I wanted to get a sense of whether this narrow change (not delegating to third-parties by default for dpr, width, viewport-width, and device-memory on Android) would pose an issue for Cloudrinary and ask if you had contacts I could reach out to at other CDNs. I saw potential use from

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

We have a non-trivial amount of usage which is relies on the legacy delegation behavior. We are working on outreach to will-be-affected customers, alerting them to the change and trying to get them to switch over to the new syntax. In at least a couple of cases the teams/devs that implemented C

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

Right now it's on track for M103, which has a branch cut in May and a release in June. I have no issue pushing this back to M104 (branch in June and release in July) to get a full 3 month buffer. Thanks for the outreach! ~ Ari Chivukula (Their/There/They're) On Thu, Apr 7, 2022 at 2:28 PM Eric

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

That's a good question! At the moment there isn't a plan to remove the legacy-named client hints (dpr, width, viewport-width, and device-memory). The messaging around this is a good opportunity to push users to the updated naming (sec-ch-dpr, sec-ch-width, sec-ch-viewport-width, and sec-ch-device-m

Re: [blink-dev] Intent to Remove: Legacy Client Hint Mode

Thank you for the ping Eric. For ImageEngine , the impact of removing the legacy delegation behaviour of dpr, width, viewport-width, and device-memory will be minor as ImageEngine has fallback mechanisms that will limit any negative impact. The challenge is more about h