User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

Typed "firefox" in the address bar.
Pressed CTRL+ENTER.

Actual results:

http://www.firefox.com was entered.

Expected results:

I'm requesting an option to fixup with https.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

May be a duplicate but didn't find it yet.

Backed out for bc failures on browser_tabDrop.js

Backout link: https://hg.mozilla.org/integration/autoland/rev/d719cd701127b18e996f45d1198bc48b3023f686
Log link: https://treeherder.mozilla.org/logviewer?job_id=323444629&repo=autoland&lineNumber=2592

https://hg.mozilla.org/mozilla-central/rev/a4ca06311d43

Folks, you just broke so many websites for people that use ctrl+enter to access sites that don't run a properly configured https and didn't intend to send anyone to https. Chrome and edge don't work this way. So end-users are seeing what is fairly described as "websites broken on firefox only". It's cool that you added an option "browser.fixup.alternate.protocol" , but you chose the wrong default.

This is an advanced feature, undiscoverable by non-technical users. The users of this feature are capable of using about:config to adapt it to their needs. We're moving towards https since it's the direction the Web is going.