On Tue, Nov 2, 2021 at 9:14 AM Ari Chivukula <[email protected]> wrote:
> Contact emails > > [email protected], [email protected], [email protected] > > Design Doc > > > https://docs.google.com/document/d/1yhVLyEIpDhhDQf698WkvXBiPcLwxEgCBI4o1FjvXwfM/edit > > > https://docs.google.com/document/d/1X5bEbIZ9U2DQhB_4yWxVuR9rGnnWjAOW-gSdlINbnNU/edit > > Specification > > https://wicg.github.io/client-hints-infrastructure/ > > https://wicg.github.io/responsive-image-client-hints/ > > https://wicg.github.io/savedata/#save-data-request-header-field > > https://wicg.github.io/netinfo/#networkinformation-interface > > Summary > > Now that our implementation aligns with the Client Hint proposal > <https://wicg.github.io/client-hints-infrastructure/> and the new names > for existing client hints with the `sec-ch-` prefix are launched, we should > alert web developers to migrate to them. The best way to do this is by > introducing a new Client Hints DevTool issue > <https://docs.google.com/document/d/1lDEvj8tMeuvUs1HTTqL-44YiI-7ljeQkusM_WhUfIeE/edit> > . > > Blink component > > Privacy>Fingerprinting > <https://bugs.chromium.org/p/chromium/issues/list?q=component%3APrivacy%3EFingerprinting> > > Motivation > > Client Hints <https://www.chromestatus.com/feature/5995832180473856>, a > method to request information about the user's device or conditions, have > been implemented in Chrome, but since the initial implementation the naming > scheme has changed. If implemented, this proposal would alert developers > using `dpr`, `width`, `viewport-width`, and `device-memory` to migrate to > use `sec-ch-dpr`, `sec-ch-width`, `sec-ch-viewport-width`, and > `sec-ch-device-memory` respectively. The three network related client hints > with legacy names, `rtt`, `downlink`, and `ect`, will not be updated as > they may be replaced by different hints in an independent process. > > TAG review > > Not needed > > Risks > > Only Blink implements client hints and we are not (yet) removing any > current ones, just pushing developers to use the corrected names. If usage > permits, we will remove the legacy names down the line in another intent. > > > Interoperability and Compatibility > > Gecko: No official position; mild positive signals. > <https://lists.webkit.org/pipermail/webkit-dev/2020-May/031198.html> > Note that this is Webkit rather than Gecko. :) > Firefox: UA Client hints considered non-harmful > <https://mozilla.github.io/standards-positions/#ua-client-hints> > > Web developers: Positive interest from Cloudinary > <https://discourse.wicg.io/t/responsive-image-client-hints-call-for-review/5470> > > Is this feature fully tested by web-platform-tests? > > N/A (the issues tab isn’t in other browsers) > <https://chromium.googlesource.com/chromium/src/+/refs/heads/main/third_party/blink/web_tests/external/wpt/client-hints/> > > Tracking bug > > https://crbug.com/1227043 > > Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/feature/6658223894429696 > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGpy5DJq4f6LvkROvh83M%3D%2Bd85DMBYdS05ofjKj4VyRFtuGh4w%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGpy5DJq4f6LvkROvh83M%3D%2Bd85DMBYdS05ofjKj4VyRFtuGh4w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANh-dX%3DWwwaSc8vSef3JYzVH9OUqUzp8xXLAtv1L%3DvWEk9_8%3DA%40mail.gmail.com.
