Windows 10: Mailto: in Browsers not working

I'd like to think so but I'm not hopeful as there doesn't seem to have been any input from a Microsoft employee on this thread.

 

How can they get feedback? I mean, Windows 10 has been out for over a year now. Microsoft is not known for listening to their customers.

 

Everyone that has contributed to this thread is a Junior Member.

Seems to reflect something odd - why aren't more experienced - longer time users on this thread or indeed complaining about this issue!

 

I am having the same email issue with Windows 10.

 

Coincidence does not prove causality

( for some reason, this reply editor is putting text at the end of lines, unto the line above it, instead of wrapping into the next )

 

Probably they don't see it as an issue. Their experience tells them that not all the settings can be reached through the Settings app. Some of them can still only be found in Control Panel. Apparently this is where you have to go to set the MAILTO protocol....

http://answers.microsoft.com/en-us/w...60d29dd?auth=1

 

I already accessed and set those settings, and it still won't work from any browser.

 

I see the same thing now and then, thought it was just me. It even will do it in the middle of a line.

 

That does sometimes happen... there are a couple of formatting quirks- like adding text after you've a URL shown in your post - e.g. when editing it, or changing back from italics or bold e.g.

You know about the protocol setting in the control panel; you can also try this if it's not been mentioned for your particular email client:

 

It just dawned on me that it happens when using Reply With Quote.

 

- works fine for me with Firefox.. to start with. But sometimes what you describe happens when typing and modifying a reply - but I've never quite noticed what causes it.

 

Thread has gone off on a tangent... *Tongue

 

The seem to have "fixed" this in the Anniversary release by locking the MAILTO protocol down to MAIL. No other choices.

 

Does this help? This bit looks promising...

http://superuser.com/questions/97246...ram-not-listed

 

I don't use that browser. Not sure why it would help. The problem is happening, no matter which browser I use, since "upgrading" to Windows 10.