This is an odd wording: "Allow ... [No] [Use Gmail]". This may confuse people who will think that in order to use Gmail, you have to click this button.
Oh, I should submit a bug report instead of posting here.
The wording is confusing and I had to do a double take and then click on the help to figure out what its' really wanting to let me know.
"Allow Gmail to open all email links" is terrible wording. It would seem to the average user that gmail wants to open up all the links in their email.
mailto: is getting less common (due to spambots) and personally I can't remember the last time I clicked on one of those (that wasn't a web page from 2002).
This will cause a lot of confusion and some tech support calls from family/friends.
Wouldn't it make more sense to say "Do you want to use Chrome as your default email client" or something?
The whole post is terribly worded. When I heard "email links" I naturally thought, "links in my email" and not "mailto: pseudo-protocol links." So I was very confused when it said that "an application on my computer that I never used would pop up and interrupt me" and that now the links "will open a fresh Gmail compose window."
I wrote some JavaScript code a while back which would automatically detect if a visitor was logged in to GMail, and would replace all mailto links on my page with GMail compose links instead. I never put it live on my site though as the process of detecting if a user is logged in to gmail is pretty dodgy. In case you're interested in the code, or the detection process:
Interesting experiment, but I don't think webdevs should interfere with what client should be run by the user to send the email. Mailto: works just fine, and it's up to the user to set up the client for mailto.
If you use gmail, why wouldn't you choose to do this? I'm so sick of mailto: links opening up whatever useless mail client came preinstalled on whatever computer I'm using.
A complete aside, but the pushState/client side rendering implementation on the blog surprised and confused me massively. It seems like the wrong tool for a blog.
They could at least have sent the page you're trying to load so that it's ready to render immediately (instead of having to retrieve it from the server after the "container" has loaded).
Yeah, whatever they're doing about server-side rendering is just completely failing, which is really surprising. Gmail works well without js, so it's not as if they don't have competent web devs.
Smuggling XML in a giant CSS comment is also very … special.
It took them a while to build that in. So secure and fast, but something as basic as this (which the competition got since day one) has no priority apparently.
I believe Google Calendar also asks if you want iCal files to be opened in Google Calendar. I think other sites could register as that protocol handler as well.
Seems that's intentional, even without a pinned gmail tab:
"Say yes, and clicking on email links in any application on your computer will open a fresh Gmail compose window."
http://www.w3.org/TR/html5/timers.html#custom-handlers
http://updates.html5rocks.com/2011/06/Registering-a-custom-p...