524227 - Toggle of "Warn me when web sites try to redirect or reload the page" Option Generates an Error

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[GµårÐïåñ]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3

When I toggle the option "Warn me when web sites try to redirect or reload the page" at Tools|Options|Advanced|General|Accessibility, it immediately generates the following error in the console:

Error: Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]
Source file: chrome://browser/content/preferences/advanced.js
Line: 222

and if you repeat the process it will continue to generate the same error, such as this when I toggle it again:

Error: Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]
Source file: chrome://browser/content/preferences/advanced.js
Line: 222

I am not quite sure what is causing this error and the search for this error results in nothing that is relevant to how I am getting the error, so not sure what is going on. Any help would be appreciate to find out what this bug is and how to fix it.

Reproducible: Always

Steps to Reproduce:
1. Start Browser
2. Open Error Console (I use Console2 and you can open after the fact too)
3. Toggle: Tools|Options|Advanced|General|Accessibility|"Warn me when web sites try to redirect or reload the page"
4. Error Occurs!
5. Repeat the process toggle again, watch error show up again.
Actual Results:  
Error is generated and the redirect warning does not occur.

Expected Results:  
There is no error and the redirect is stopped, notified to the user.

I have no additional information other than what I have presented and there is no crash report as the browser doesn't crash, just generates an error in the console and the function is not available, nothing else.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5pre) Gecko/20091014 Shiretoko/3.5.5pre

I tested this but was not able to reproduce.
Have you already tried safe-mode / new profile?
http://support.mozilla.com/en-US/kb/Safe+Mode
http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile

Comment 2

[GµårÐïåñ]

(In reply to comment #1)

I had not done it in safe mode, just with a clean profile. I just did it in safe mode and I get one extra error:

It first generates:

Error: undefined entity
Source file: jar:file:///C:/Users/<>/AppData/Roaming/Mozilla/Firefox/Profiles/<>/extensions/[e-mail]/chrome/nnl-inner.jar!/global/globalBindings.xml
Line: 70, Column: 5
Source code:
    <content chromedir="&locale.dir;"

and then it generates the previously shared error of:

Error: Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]
Source file: chrome://browser/content/preferences/advanced.js
Line: 222

Now what bothers me is that the above error reference to nnl suggests that I have it running but I am in safe-mode so there is obviously no theme element, so... why is this error coming up? Other than that, same results, anything else I can try to eliminate my installation as the problem and verify that it is indeed an Fx issue or not?

Comment 3

[GµårÐïåñ]

(In reply to comment #1)

Also, your UA suggests that you are on a different build than me, not sure if it was used for your testing or just to post the reply. If it was used for the testing, that could suggest the reason you are not seeing it, if it was just for posting, then my apologies.

Comment 4

[Ria Klaassen (not reading all bugmail)]

I'm using the latest 3.5 test build. Do you still see a problem if you go to your profile and drag this nasanightlaunch extension out of the window?
http://support.mozilla.com/en-US/kb/Profiles

Comment 5

[GµårÐïåñ]

(In reply to comment #4)

I am not sure if its a language barrier but what you said makes no sense to me. What do you mean go to your profile and "drag this nasanightlaunch extension out of the window"? If you are asking me to uninstall it, no I won't because in Safe Mode or clean profile without the theme installed it should not be a factor. If you are talking about something else you need to be more clear and I don't need links to documents, I am not a novice, just say it but make sure it makes sense. Thanks.

Comment 6

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 7

[Tyler Downer [He/Him]]

This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.

Comment 8

[GµårÐïåñ]

Actually I didn't get anything from you or the system like you suggested two weeks ago until today when you posted the latest reply. So I am not sure why the system didn't notify me until now, but regardless, I have not seen this issue for a while specially since NoScript has a built-in fix that has successfully made this obsolete. So if you want to close it because it has been fixed, go for it, if you want to close it because no one wants to look into it, your prerogative but as a developer, I find that a bad move unless you are too focused on the next release to care and hope that everyone will just dump and run.

Comment 9

[Tyler Downer [He/Him]]

So you see the issue you reported in comment 0 With Firefox 3.6.15 in a fresh unmodified profile?

Comment 10

[Tyler Downer [He/Him]]

This bug has had the CLOSEME tag for several weeks and the date in the tag is
far gone. If the reporter can still see this issue, Please retest with Firefox
3.6.x or later and a new profile
(http://support.mozilla.com/kb/Managing+profiles). Then please remove the
closeme tag in the whiteboard, mark the bug against the proper version and
comment on the bug.

Comment 11

[GµårÐïåñ]

(In reply to comment #9)

I wasn't able to reproduce it with the latest version that I am running (3.6.15) but to be honest I didn't exactly try super hard to make it break, I am over it. But the 3 times I tried, nothing happened, so you can close it if you want with no resolution and if someone else finds a problem and opens it again, take it from there.