Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Enter and Ctrl-Enter stopped working in the address bar since 3.6.13

  • 1 பதிலளி
  • 1 இந்த பிரச்சனை உள்ளது
  • 2 views
  • Last reply by John99

Since 3.6.13, Enter and Ctrl-Enter no longer do anything at all in my address bar in Firefox. I uninstalled Firefox (including all user settings and preferences) and reinstalled fresh, and was amazed to see that the problem is still the same. If I type "example" and hit Ctrl-Enter, unlike before, I don't get the "http://www." and ".com" filled in for me. If I type "www.example.com" and press Enter, the browser doesn't go there. The only way I can get it to take action on a URL is to use the mouse to click the right-arrow icon at the right end of the address bar.

I posted this earlier and can't find the previous post (searching for Ctrl-Enter and Control-Enter did not find it). Someone suggested that I had a problem with my FF user profile, but uninstalling (with the complete option including settings/prefs) and reinstalling should have fixed that, no?

Since 3.6.13, Enter and Ctrl-Enter no longer do anything at all in my address bar in Firefox. I uninstalled Firefox (including all user settings and preferences) and reinstalled fresh, and was amazed to see that the problem is still the same. If I type "example" and hit Ctrl-Enter, unlike before, I don't get the "http://www." and ".com" filled in for me. If I type "www.example.com" and press Enter, the browser doesn't go there. The only way I can get it to take action on a URL is to use the mouse to click the right-arrow icon at the right end of the address bar. I posted this earlier and can't find the previous post (searching for Ctrl-Enter and Control-Enter did not find it). Someone suggested that I had a problem with my FF user profile, but uninstalling (with the complete option including settings/prefs) and reinstalling should have fixed that, no?

All Replies (1)

Your last post is here