Microsoft Removes Feature in Edge to Enhance User Data Privacy

Microsoft Removes Feature in Edge to Enhance User Data Privacy

Microsoft Discontinues Legacy Method for Enhanced Privacy

In a significant move aimed at bolstering user privacy, Microsoft has announced the discontinuation of the window.external.getHostEnvironmentValue() method. This Edge-exclusive, non-standard technique for accessing user device and browser data is being replaced by a more privacy-centric solution: the User-Agent Client Hints API.

Understanding the Transition to User-Agent Client Hints

In its announcement, Microsoft emphasized the shift away from the deprecated method, stating:

The window.external.getHostEnvironmentValue() method is an Edge-only, non-standards-based way for web developers to access information about the browser and platform….we’re announcing our plan to deprecate this method and we’re asking web developers to use the standardized User-Agent Client Hints API instead.

The rationale behind this decision is clear. Microsoft aims to enhance browser privacy by minimizing user fingerprinting practices. As explained:

Our decision to deprecate the getHostEnvironmentValue() method is driven by our goal to enhance browser privacy by eliminating user fingerprinting. The UA Client Hints API provides browser and platform information in a much more privacy-preserving way as browsers can decide what to return when asked for hints. Low entropy hints are accessible with every request, while the high entropy hints that can potentially give away more fingerprinting information can be gated with user preferences or behind a permission request.

By utilizing the User-Agent Client Hints API, websites can still obtain necessary browser and platform details, but with a significantly reduced data footprint left by users during their online activities. This ensures a more tailored browsing experience while upholding privacy standards.

Deprecation Timeline and Steps

Microsoft has outlined a systematic approach for the deprecation process, which will occur in three phases culminating in a complete removal by October 2025. This timeline is strategically aligned with the end of support for Windows 10. The steps include:

To reduce interoperability issues and to gather feedback, we’re planning to deprecate the non-standard getHostEnvironmentValue() method by following these steps:

Edge Version Release Date Deprecation Step
Edge 135 April 3, 2025 The DevTools Console warns developers when their code uses the method. Developers can use a feature flag to test sites with the method disabled.
Edge 137 May 23, 2025 The method will be disabled but can still be utilized by requesting a temporary extension for specific domains.
Edge 141 (subject to developer feedback) October 2025 The method will be fully eliminated from Edge.

Future of User Privacy

For developers whose websites have historically depended on the getHostEnvironmentValue() method, Microsoft has indicated that extension requests will be accommodated. For further information, refer to the detailed announcement on their official blog post.

This significant change reflects a broader industry trend towards enhanced user privacy, positioning Microsoft at the forefront of this vital initiative.

Source & Images

Related Articles:

Microsoft Hikes Prices on All Standalone On-Premises Server Products
Monster Hunter Wilds Update #1 Released on All Gaming Platforms

Leave a Reply ▼

Your email address will not be published. Required fields are marked *