The browser version is always already accessible, and even in future plans to reduce user agent info (https://www.chromestatus.com/feature/5704553745874944 http

The browser version is always already accessible, and even in future plans to reduce user agent info (https://www.chromestatus.com/feature/5704553745874944 https://www.chromestatus.com/feature/5704553745874944) the major version number is never going to be hidden. This API exposes zero new fingerprinting bits. Meanwhile userspace solutions for the same solution are a) occasionally buggy b) not as widely used as they should be c) not as performant as they could be if implemented directly within the browser and d) not automatically updated as new browser features are released. Standardizing this will improve all of that. It is valuable to standardize APIs and build them into the web for features like this where there's a clearly correct approach that's required by a large percentage of modern sites (anything with client side dynamic content). Having browser vendors implement this, embedded in the browser itself and supported by browser implementers directly, is a free security win for the web.