266901 - URL bar locks and wil not respond to links

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Don Luchini]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

At times, the URL bar will no longer respond to links. For example, if I go to
http://bugzilla.mozilla.org and click on a link that takes me to
some_other_page.html, the URL bar will continue to sho
http://bugzilla.mozilla.org even if I am at
http://bugzilla.mozilla.org/some_other_page.html. The Back, Forward, and Stop
buttons will also be greyed out, and Reload will take you back to what is
displayed in the URL bar and not where you are. This could potentially allow a
website to spoof as another.

Reproducible: Sometimes
Steps to Reproduce:
1. Continue normal browsing; the URL bar will occasionally lock. I do not know
what causes this to happen, since it does not occur at any given time or on any
given page.
Actual Results:  
The URL bar along with the Back, Forward, Reload, and Stop buttons will not
perform correctly, and the URL bar will stay in one location.

Expected Results:  
The URL bar should always display the URL a person is visiting.

I found this bug in Netscape 7.2, but have verified its existance in the Mozilla
1.7.3 release (but I have not tested in a recent nightly).

Comment 1

[Jesse Ruderman]

Do you see any errors from chrome javascript in Tools > JavaScript console when
this happens?

Comment 2

[Don Luchini]

I never thought to check that. I'll wait until it happens again, then see if it
happens again. I did have a Netscape window open with the problem and started
using Firefox, but then Windows Update decided to restart my computer without
asking. So, when it does happen, I'll have more info.

Comment 3

[Jesse Ruderman]

You have to go to about:config and set javascript.options.showInConsole to true
for chrome JavaScript errors to appear in the JavaScript console.  Sorry for not
saying that before.

Comment 4

[Don Luchini]

OK, I will look into that, thanks for the pointer otherwise I would have
tortured myself looking for an error.

Comment 5

[Don Luchini]

OK. I haven't had the bug reoccur yet, but upon starting Netscape I will receive
the following JavaScript Error Messages: 

1) Redeclaration of const JS_LIB_LOADED in chrome://jslib/content/jslib.js on
Line 32

2) aimPrefsManager is not defined in chrome://aim/content/AimIM.js on Line 106

3) redeclaration of MSG_FLAG_NEW in chrome://aim/content/AimMailBridge.js on Line 2

4) Redeclaration of const kDefaultSortColumn in
chrome://messenger/addressbook/abCommon.js on line 50

I know that errors 2, 3, and 4 are caused by the AIM client. Error 1 is probably
something to do with one of the JSLib-enabled extensions I have, probably the
Netscape Search Toolbar.

After browsing to this page, but no others, I will also receive these messages:

1) pt has no properties in chrome://navigator/content/sidebarButton.js on line 25

2) redeclaration of const RDF_NS in
chrome://communicator/content/bookmarks/bookmarks.js on line 38

3) p.onLinkIconAvailable is not a function in
chromeL//global/content/bindings/tabbrowser.xml on line 641

I will test to see what happens in Mozilla 1.7.3 momentarily, to see if any of
the above happens.

Comment 6

[Daniel Veditz [:dveditz] (OOO: back Aug 26)]

Clearing confidential flag, no evidence this could be hacker-induced, just a bug.

Comment 7

[Don Luchini]

I've had 1.8a5 for a few hours now and have been using it as the default
(alongside Netscape 7.2 on a different profile). So far, I haven't been able to
reproduce this bug, but I will wait and see what happens.

BTW, upon starting Mozilla 1.7.3, I do not receive any JavaScript error
messages, even after enabling the javascript.options.showInConsole pref in
about:config. I also have not been able to repeat the error in Mozilla 1.7.3
since when I found it in the first place in 1.7.3...

Either way, this bug only occured six or seven times in NS7.1/7.2 and the one
time I found it with 1.7.3, so I'm guessing that it's not something that
reoccurs a whole lot.

Comment 8

[Don Luchini]

OK, I've got it happening again in Netscape 7.2, but not Mozilla 1.8a5 (at the
moment, haven't tested yet). However, I DO have a URL that the bar will lock up
at (interesting enough, the problem is at my own website). Check out
http://www.angelfire.com/tn3/hardwarehacks/IE.html and then try using the Back
button. If what's happening to me is happening to you, the back button will not
be working. Now try visiting some other link, and the URL bar will be frozen at
http://www.angelfire.com/tn3/hardwarehacks/IE.html until you restart Mozilla.
I'm using W3-compliant HTML 4.01 in the code, but Angelfire adds their own code
to the page (which makes it display ads), which is probably the problem.

I don't know if this happens every time; I have yet to verify that.

Comment 9

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 10

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.