971221 - Dialogs created by add-ons bug the Awesome Bar (location bar)

Status: RESOLVED WORKSFORME

(Firefox :: Address Bar, defect)

Description

[Dario Gjorgjevski]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140211030201

Steps to reproduce:

I have tested and confirmed this with two completely unrelated add-ons (NoScript and LastPass).

First, using NoScript: make sure NoScript is installed and add-ons are forbidden globally (this is required so that allowing them afterwards creates a dialog asking for user confirmation). Reproduce the bug with the following steps:

1) Again, make sure scripts are forbidden globally (see explanation above);
2) Open a new tab;
3) Type something into the Awesome Bar (location bar);
4) Allow scripts globally via NoScript (this will open a dialog asking for user confirmation and trigger the bug);
5) Now, you cannot navigate to the address you typed into the Awesome Bar, no matter if you press Enter, Ctrl+Enter, Shift+Enter or any other combination that can be used. If, however, you switch to another tab and then come back, everything will be just OK.

The same can be done with LastPass by opening the add-on's login dialog (being logged off and clicking on the toolbar button) instead of opening NoScript's dialog for allowing scripts.


Actual results:

I could not navigate to the URL typed into the Awesome Bar (location bar).


Expected results:

I should have been able to navigate to the URL typed into the Awesome Bar (location bar).

Comment 1

[Rika Pi]

I have replicated bug in windows 8.1
using NoScript
nightly build 30.0a1
also blocking script again will make text in the nav bar dissapear.
another observation.
if you set NoScript to allow script in newtab text will remain
but will not respond to pressing enter and when clicking the relode button in the nav bar dissapears as well.

I wonder if we can replicate this in non 30.0a1 builds?
or in diffrent platforms.

by the way I'm a new bug tester and am still learning the ropes.

Comment 2

[Liz Henry (:lizzard) (relman/hg->git project)]

Rika Pi, thanks for replicating the bug!    It would probably be a good idea to try this on the latest Firefox 29 build if you'd like to do that. But this is enough to mark the bug as NEW  which is a good start.

Comment 3

[Rika Pi]

I have confirmed it in Firefox beta 28.0b4

Comment 4

[Rika Pi]

I have confirmed bug in Firefox 29.0

Comment 5

[Dario Gjorgjevski]

The bug appears to have been fixed in 31.0a1 (2014-03-18). Can anyone confirm this?

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to Дарио Ѓорѓевски from comment #5)
> The bug appears to have been fixed in 31.0a1 (2014-03-18). Can anyone
> confirm this?

this is enough to close the bug.  However, if  Rika Pi wants to confirm that'd be cool too.