On Browser-Specific URL Schemes

URL schemes, such as "http://..." or "ftp://...", are fundamental components of the web, yet surprisingly malleable. While seemingly low-level, developers can register custom URL schemes within their applications. This allows for directing users to specific applications, even overriding default browser settings.

A prime example is Microsoft Edge's microsoft-edge:// scheme. Using this scheme forces links to open in Edge, regardless of the user's default browser. This capability raises concerns about user control and browser choice.

Daniel Aleksandersen's EdgeDefelector program countered this behavior, highlighting the importance of respecting user preferences. The recent adoption of the microsoft-edge:// scheme by Brave and Firefox underscores the significance of this issue. Failure to support such schemes could render links unusable.

While much discussion centers on Windows 11, this behavior is observable across browsers on macOS.

The origins of this practice are rooted in iOS. Before iOS 14, default browser changes were impossible. To integrate its apps, Google introduced the googlechrome: scheme in 2014, allowing redirection to Chrome from other Google services. While seemingly Google's action, Apple's approval is the key factor. Microsoft's adoption of this approach is seen as mirroring Google's past practice.

Ideally, software should intercept these browser-specific schemes and open links within the user's currently active browser. The web should be a unified experience, independent of any specific browser.

The above is the detailed content of On Browser-Specific URL Schemes. For more information, please follow other related articles on the PHP Chinese website!