Autofill disabled on new Microsoft login page. ANNOYING!!!

I tried the inspector in firefox and although I was able to change it to "autocomplete on" it did nothing when I restarted the page after signing out and then in and out again.  So I went back to the inspector and there it is again

"autocomplete off"   Is there something Im missing?

Timbow0,

You are not missing anything. Changes made to a page's HTML using Firefox's Inspector are not permanent. When you reload the page, the changes are lost.

To make changes (to a page's HTML) that will persist across reloads, you will need to run a user script.

For Firefox, download and install the free add-on called Greasemonkey. That add-on will allow you to run user scripts. Then install the script I posted in this thread on May 11, 2016 ... that script will essentially change autocomplete to "on" each time the sign on page loads.

Once you have installed the script, you may have to enter your email address once into the sign in page for Firefox to remember it. There-after, Firefox will auto-complete your email address when you type the first character into the sign-on page.

Note that in order for Firefox to "remember" your email address for auto-complete,  you must NOT enable the Firefox option to clear history.

Hope this helps.

Hey Thanks for the reply!  I think Im going to wait for hotmail to fix this as I am not too comfortable screwing around that much.  If they dont fix it soon I will change my email account.  I only give them so much leeway after all the **** they try to put people through.  Some day they will learn that customers are the life blood of any business.

Timbow0,

I understand your decision. If you do not feel comfortable installing and running user scripts then you should not attempt to do so.

Unfortunately, I do not think that Microsoft is ever going to fix this problem. The solution is trivial .... all Microsoft has to do is change autocomplete="off" to   autocomplete="on". This problem started when the new sign on page was released around March 24. It's been almost 2 months since then ... that's plenty if time for Microsoft to have fixed this problem ... if they intended to fix it. Thus, it appears that Microsoft has no intention of fixing this problem.

I opened a Support Request with Microsoft's Answer Desk (about this  problem). They stopped responding to my Support Request ... another indication that Microsoft has no intention of fixing this problem. 

Microsoft-engaged Forum Moderators and Support Engineers have also stopped responding to this (and other) threads (here in Microsoft Community) that complain about this problem.

Microsoft does not care about Customer Satisfaction.  As you said, the best alternative might be to use another email service.

Thank you langware!

Your solution works for me, and I am not a code writer by any means.

I do feel a touch uneasy about applying a "fix" or "work-around" to a situation easily corrected by the page author!

Yet Microsoft continues to obfuscate. (big surprise) 

Will any Micro$oft representative explain the reason for this inconvenient "update"?

I can't quite tell, but it seems the whole "Microsoft Support" meme is either

Museum quality, Weapons grade, or Meticulously calculated to third decimal precision, Stupid.