Re: [w3ctag/design-reviews] Markup based Client Hints delegation for third-party content (Issue #702)

@ylafon / @torgo 
Can this be re-opened? We're revising this proposal with updated syntax: https://groups.google.com/a/chromium.org/g/blink-dev/c/cGOjmfOamsE


Old:
```<meta name="accept-ch" value="sec-ch-dpr=(https://foo.bar/  https://baz.qux), sec-ch-width=(https://foo.bar)">```
  
New:
```<meta http-equiv="delegate-ch" value="sec-ch-dpr https://foo.bar https://baz.qux; sec-ch-width https://foo.bar">```

We’re switching from `name="accept-ch"` to `http-equiv="delegate-ch"` on [advice](https://github.com/w3ctag/design-reviews/issues/702#issuecomment-1143680791) that `http-equiv` should be used when the value is impacting the processing model. We’re switching from syntax close to [HTTP Permissions-Policy](https://w3c.github.io/webappsec-permissions-policy/#permissions-policy-http-header-field) to use syntax closer to the [iframe allow attribute](https://html.spec.whatwg.org/dev/iframe-embed-object.html#attr-iframe-allow) at the request of [developers](https://github.com/WICG/client-hints-infrastructure/issues/108).
 
Although this change is coming after a launch in M100, [usage](https://chromestatus.com/metrics/feature/timeline/popularity/4081) of the prior syntax is low (currently 0.000016%) and it seems worth taking the opportunity to reduce developer confusion and increase standards compliance.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/702#issuecomment-1155464030

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/702/1155464030@github.com>