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

I can't provide an official answer for WebKit. CC: @othermaciej

> Ok, so it really comes down to wether having the new structured data is worth the implementation effort here. 

Personal answer: CH is surely not any worse than what we have now. But WebKit's bar for feature inclusion is pretty high, and the benefit doesn't seem great.

What would _really_ incentivize implementation would be to combine CH with some _very aggressive_ plan to make it harder to detect what browser is in use, e.g. remove the Sec-CH-UA hint from the spec, then pair CH with a plan to pare down existing UA strings on all browsers, even if it temporarily breaks some websites. Think "remove the string 'Chrome' from the user agent" level of change. Then I could get excited about CH. That would be a pretty huge change though, and I doubt it's in the cards.

-- 
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-895663999