New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 660062 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Chrome registers as a default handler for email on Windows

Reported by jro...@microsoft.com, Oct 27 2016

Issue description

Version: 54.0.2840.71 m (64-bit), Version 56.0.2902.0 canary (64-bit)
OS: Windows 10 - build 14951

What steps will reproduce the problem?
(1) Open the Windows Settings app
(2) Browse to System > Default Apps
(3) Click to change your default Email handler
(4) Select Chrome

What is the expected output?
Either Chrome does not register as an email handler or it actually handles email.

What do you see instead?
Choosing Chrome as your email handler will cause mailto: links to launch Chrome, but nothing happens.
 
defaultapps.PNG
107 KB View Download

Comment 1 by jsc...@chromium.org, Oct 28 2016

Cc: jsc...@chromium.org
Status: WontFix (was: Untriaged)
This is working as intended, to support webmail clients that use navigator.registerProtocolHandler for registering the mailto handler. We've considered making the handler available only when a site has registered for mailto, but that seems like a more confusing user experience, particularly when you factor in corner cases like multi-profile. So, the current behavior of making it an optional handler seems the least worst solution.
I assumed that was what this was for. Though I tried the top three webmail clients (Gmail, Yahoo, Outlook) and none seem to support this. Maybe I'm missing a step.  

So that makes me question the user value here compared to the confusion it causes in the base case where it is broken and doesn't actually handle mailto.

Perhaps a simplified design is to wait to register until the first site calls registerProtocolHandler? It's probably overkill to manage handling multiple profiles and such. But at least waiting until Chrome has ever seen a site that wants this seems like a huge user experience improvement  over the current behavior.

Sign in to add a comment