search

WICG / ua-client-hints

Wouldn't it be nice if `User-Agent` was a (set of) client hints?
https://wicg.github.io/ua-client-hints/
Other
590 stars 77 forks source link

Awareness of location for User Agent Reduction issues #300

Closed jwrosewell closed 2 years ago

jwrosewell commented 2 years ago

The CMA have published their first report following the commitments agreed with Google in February 2022.

Going forward, Google plans to monitor several metrics, including: Net.HttpResponseCode (material changes in the number of requests that failed to deliver content), ClientHints.StoreLatency (captures the time it takes, in milliseconds, to store the client hints for an origin in the PrefsService), ClientHints.FetchLatency (captures the time it takes, in milliseconds, to retrieve the client hints for an origin from the PrefsService, that will be added to the outgoing HTTP request headers), ClientHints.CriticalCHRestart (measures the number of times a navigation had to be restarted in order to include the requested client hints on the initial navigation) and PageLoad.PaintTiming.NavigationToFirstContentfulPaint (measures the latency, in milliseconds, from the time the navigation stats to the time the response first statss getting painted to the screen). Google will also work with partner teams, both internal and external, to receive feedback and metrics on client hints latency from the server’s perspective and will monitor community reports through Chromium and issues reported on the Github repository.

The GitHub repository for raising reports is one under @miketaylr's account which I was unaware was a Google official location for raising issues on such changes.

miketaylr commented 2 years ago

Thanks for the feedback James. Given that this repo is for feedback related to the UA-CH proposal—not UA Reduction—I will close this issue. If people prefer to provide feedback as bug reports against the Chromium project, rather than GitHub issues, they can do so in the bug tracker you linked above.