[blink-dev] Intent to Prototype: Standardize existing client hint naming
Ari Chivukula
Contact emails
ari...@chromium.org, jadek...@chromium.org, mike...@chromium.org
Design Doc
https://docs.google.com/document/d/1yhVLyEIpDhhDQf698WkvXBiPcLwxEgCBI4o1FjvXwfM/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
This proposal seeks to align our implementation with the Client Hint proposal by adding the `sec-ch-` prefix where it’s missing.
Blink component
Motivation
Client Hints, 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 add new client hints with a `sec-ch-` prefix to re-implement the following: `dpr`, `width`, `viewport-width`, `device-memory`, `rtt`, `downlink`, and `ect`.
TAG review
Not needed
Risks
Only Blink implements client hints and we are not (yet) removing any current ones, just re-implementing existing ones under the correct name. If usage permits, we will remove the legacy names in the future.
Interoperability and Compatibility
Gecko: Client hints not implemented
WebKit: Client hints not implemented
Web developers: Positive interest from Cloudinary
Is this feature fully tested by web-platform-tests?
Tracking bug
Link to entry on the Chrome Platform Status
Mike Taylor
Joshua Bell
--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7162dcb1-279f-b0f6-4502-6ceb1013980d%40chromium.org.