This hint indicates the "form-factor" of the user-agent / device, so that the site can tailor its response.
If other browsers do not implement this hint, then the information will only be available in Chrome, and other browsers will implicitly return an empty value.
None - this fits with existing, similar client hints.
No activation risks - developers will always need to handle the situation where this hint is unavailable.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No change to existing behavior; this adds a new hint which sites must opt in to. Killswitch is available: ClientHintsFormFactor
No changes in the checklist apply.
Included in existing tests for other client hints: https://wpt.fyi/results/html/webappapis/system-state-and-capabilities/the-navigator-object/navigator_user_agent.https.html?label=experimental&label=master&aligned https://wpt.fyi/results/workers/WorkerNavigator_userAgentData.https.html?label=experimental&label=master&aligned
Shipping on desktop | 123 |
DevTrial on desktop | 122 |
Shipping on Android | 123 |
DevTrial on Android | 122 |
Shipping on WebView | 123 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No open issuesContact emails
djmi...@chromium.orgExplainer
https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.mdSpecification
https://wicg.github.io/ua-client-hints/#sec-ch-ua-form-factorDesign docs
https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.mdSummary
This hint indicates the "form-factor" of the user-agent / device, so that the site can tailor its response.
Blink component
Blink>NetworkSearch tags
ua-ch, uach, form-factorTAG review
This feature simply adds a new hint to the existing set of hints, containing data that was previously represented in the user-agent string.
TAG review status
Not applicableRisks
Interoperability and Compatibility
If other browsers do not implement this hint, then the information will only be available in Chrome, and other browsers will implicitly return an empty value.
Gecko: No signal
WebKit: No signal
--
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/CALMtyTRPFmmHkrk24dSby%2B1bqTft%3DtUG-btxP_bg4Ckx4DNarw%40mail.gmail.com.
On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev <blin...@chromium.org> wrote:Contact emails
djmi...@chromium.orgExplainer
https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.mdSpecification
https://wicg.github.io/ua-client-hints/#sec-ch-ua-form-factorDesign docs
https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.mdSummary
This hint indicates the "form-factor" of the user-agent / device, so that the site can tailor its response.
Blink component
Blink>NetworkSearch tags
ua-ch, uach, form-factorTAG review
This feature simply adds a new hint to the existing set of hints, containing data that was previously represented in the user-agent string.Although this info may be available, I suspect this can be a new channel of information for clients that override the user-agent string or where this information isn't provided in the user-agent string. I don't believe this to be a problem, but just something to consider
TAG review status
Not applicableRisks
Interoperability and Compatibility
If other browsers do not implement this hint, then the information will only be available in Chrome, and other browsers will implicitly return an empty value.
Gecko: No signal
WebKit: No signalCan you please file requests for positions for both Gecko and WebKit?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALMtyTRYw4Rs1rgusWkWVBV12RmiLq6h4k4Ku1oCAVF7%2B86MHA%40mail.gmail.com.
Thanks for the comments!On Tue, Feb 20, 2024 at 11:10 AM Vladimir Levin <vmp...@chromium.org> wrote:On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev <blin...@chromium.org> wrote:Contact emails
djmi...@chromium.orgExplainer
https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.mdSpecification
https://wicg.github.io/ua-client-hints/#sec-ch-ua-form-factorDesign docs
https://github.com/djmitche/web-explainers/blob/main/sec-ch-ua-form-factor.mdSummary
This hint indicates the "form-factor" of the user-agent / device, so that the site can tailor its response.
Blink component
Blink>NetworkSearch tags
ua-ch, uach, form-factorTAG review
This feature simply adds a new hint to the existing set of hints, containing data that was previously represented in the user-agent string.Although this info may be available, I suspect this can be a new channel of information for clients that override the user-agent string or where this information isn't provided in the user-agent string. I don't believe this to be a problem, but just something to considerThat's a good point, and likely needs to be considered for all client hints. Do you think it's worth adding an issue in https://github.com/WICG/ua-client-hints to track this?
TAG review status
Not applicableRisks
Interoperability and Compatibility
If other browsers do not implement this hint, then the information will only be available in Chrome, and other browsers will implicitly return an empty value.
Gecko: No signal
WebKit: No signalCan you please file requests for positions for both Gecko and WebKit?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2M_0ZZJd9EOZ-8fwWgcnkSc9K1FufqVR4ZzwyMS7rJ4EA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALMtyTRPFmmHkrk24dSby%2B1bqTft%3DtUG-btxP_bg4Ckx4DNarw%40mail.gmail.com.
--
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+unsubscribe@chromium.org.
(non-owner hat on) - Thanks for flagging, Domenic. We'll re-ping
the thread once we decide if we should rename it, and to what.
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/20c75133-f743-498b-be50-b24c27c7c999n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/20c75133-f743-498b-be50-b24c27c7c999n%40chromium.org.
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/CALMtyTRPFmmHkrk24dSby%2B1bqTft%3DtUG-btxP_bg4Ckx4DNarw%40mail.gmail.com.
--
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/CADsXd2M_0ZZJd9EOZ-8fwWgcnkSc9K1FufqVR4ZzwyMS7rJ4EA%40mail.gmail.com.
--
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.