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

why is the 20.0 address bar unresponsive?

  • 24 replies
  • 65 have this problem
  • 4098 views
  • Last reply by pearj

more options

I've upgraded to 20.0 from 19.0.2. Now the address bar is unresponsive. After typing in a valid URL and hitting enter (or clicking the arrow on the far right of the address bar), nothing happens. No error message or anything. If I open a new tab and click one of the tiles representing previously visited pages, everything works as expected. Bookmarks work too. I've tried resetting Firefox, to no avail. The only cure at this time is downgrading to 19.0.2 where everything works as expected.

Chosen solution

This has just been fixed a couple of hours ago in the 20.0.1 update, and I have confirmed it fixed the problem for me:

https://bugzilla.mozilla.org/show_bug.cgi?id=857672

Read this answer in context 👍 0

All Replies (4)

more options

For the people seeing this, one potentially very useful data point would be whether any exceptions show up in the "Errors" tab of the Firefox Error Console (Tools->Web Developer->Error Console), both immediately after startup/new window opening, and after attempting to press enter in the URL bar. If you could post copies of any exceptions listed there in the bug, that would be great.

more options

I will leave this thread open but please see and follow

  • Hi, we are in the company users use mobile profiles. After updating firefox to version 20 when you enter the address in the browser and press Enter, nothing ha /questions/955232

Note that thread relates mainly to corporate users often with mobile / roaming profiles. A possible workaround for corporate users is mentioned in that thread.

more options

Thanks for the input, folks - we've tracked down the issue and will work on getting the fix into Firefox 21.

more options

Chosen Solution

This has just been fixed a couple of hours ago in the 20.0.1 update, and I have confirmed it fixed the problem for me:

https://bugzilla.mozilla.org/show_bug.cgi?id=857672

  1. 1
  2. 2