Re: [w3ctag/design-reviews] User-Agent Client Hints & UA Reduction (#640)

What you propose sounds reasonable, @mcatanzaro. We should also have a similarly high bar for standardization, as per WebKit - as without implementer backing, there is little point in doing the standardization work. 

@karlcow, should we drag in a few more Mozilla folks? Maybe @tantek, as he was at present at the meeting with the Google folks. I see Mozilla's position on this remains [marked as "harmful"](https://mozilla.github.io/standards-positions/#ua-client-hints), and it echos @mcatanzaro concerns above. 

The relevant parts of Mozilla's objection to this proposal:

> In addition to not including this information [Sec-CH-UA], we would prefer freezing the User Agent string and only providing limited information via the proposed `NavigatorUAData` interface JS APIs. This would also allow us to audit the callers. At this time, freezing the User Agent string without any client hints (which is not this proposal) seems worth prototyping. We look forward to learning from other vendors who implement the "GREASE-like UA Strings" proposal and its effects on site compatibility.

@miketaylr, @yoavweiss, as the folks proposing this, are you willing to reduce the design to align more closely with what WebKit and Mozilla are requesting (maybe drop Sec-CH-UA entirely, work together to freeze the UA string, and maybe just expose the JS API)? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/640#issuecomment-895680385