When [writing this morning](https://www.otsukare.info/2021/02/15/capping-macos-user-agent), I was looking for information about Apple and WebKit. There are two threads on webkit-dev mailing list: https://lists.webkit.org/pipermail/webkit-dev/2020-May/thread.html#31195 https://lists.webkit.org/pipermail/webkit-dev/2020-November/thread.html#31571(In reply to Henri Sivonen (:hsivonen) from comment #68) Henri about I see how my comment can be misread. > (In reply to Karl Dubost💡 :karlcow from comment #67) > > Google intends to provide the real OS version number through the `Sec-CH-UA-Platform-Version` > > The blink-dev thread doesn't document any proper use case for exposing the operating system version. More exactly Rick Byers [says](https://groups.google.com/a/chromium.org/g/blink-dev/c/hAI4QoX6rEo/m/tPxfPScoAQAJ): > LGTM2 to fix the UA string, but only after some API (Sec-CH-UA-Platform-Version or anything else) is fully available as a work-around. I didn't say it was done in any official way. Now I think it would be hasty to use the capping as a justification for clients hints, hence the ongoing discussion.
Bug 935216 Comment 70 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When [writing this morning](https://www.otsukare.info/2021/02/15/capping-macos-user-agent), I was looking for information about Apple and WebKit. There are two threads on webkit-dev mailing list: https://lists.webkit.org/pipermail/webkit-dev/2020-May/thread.html#31195 https://lists.webkit.org/pipermail/webkit-dev/2020-November/thread.html#31571 (In reply to Henri Sivonen (:hsivonen) from comment #68) Henri about I see how my comment can be misread. > (In reply to Karl Dubost💡 :karlcow from comment #67) > > Google intends to provide the real OS version number through the `Sec-CH-UA-Platform-Version` > > The blink-dev thread doesn't document any proper use case for exposing the operating system version. More exactly Rick Byers [says](https://groups.google.com/a/chromium.org/g/blink-dev/c/hAI4QoX6rEo/m/tPxfPScoAQAJ): > LGTM2 to fix the UA string, but only after some API (Sec-CH-UA-Platform-Version or anything else) is fully available as a work-around. I didn't say it was done in any official way. Now I think it would be hasty to use the capping as a justification for clients hints, hence the ongoing discussion.
When [writing this morning](https://www.otsukare.info/2021/02/15/capping-macos-user-agent), I was looking for information about Apple and WebKit. There are two threads on webkit-dev mailing list: https://lists.webkit.org/pipermail/webkit-dev/2020-May/thread.html#31195 https://lists.webkit.org/pipermail/webkit-dev/2020-November/thread.html#31571 Henri about > (In reply to Henri Sivonen (:hsivonen) from comment #68) > > (In reply to Karl Dubost💡 :karlcow from comment #67) > > Google intends to provide the real OS version number through the `Sec-CH-UA-Platform-Version` > > The blink-dev thread doesn't document any proper use case for exposing the operating system version. I see how my comment can be misread. More exactly Rick Byers [says](https://groups.google.com/a/chromium.org/g/blink-dev/c/hAI4QoX6rEo/m/tPxfPScoAQAJ): > LGTM2 to fix the UA string, but only after some API (Sec-CH-UA-Platform-Version or anything else) is fully available as a work-around. I didn't say it was done in any official way. Now I think it would be hasty to use the capping as a justification for clients hints, hence the ongoing discussion.