[Exception... "'JavaScript component does not have a method named: "onLocationChange"' when calling method: [nsIWebProgressListener::onLocationChange]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "JS frame :: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsSessionStore.js :: sss_observe :: line 338" data: no]
file:///C:/Program%20Files/Mozilla%20Firefox/components/nsSessionStore.js
Line 338
[Exception... "'JavaScript component does not have a method named: "onLocationChange"' when calling method: [nsIWebProgressListener::onLocationChange]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Line 0
Noticed this after I upgraded to Firefox 3.6. The bottom error pops up in the Firebug console after every navigation, both errors appear when clearing the history.
Disabled all plugins except FlashGot and Firebug to verify that FlashGot was the source of the errors.
nsIWebProgressListener::onLocationChange error
nsIWebProgressListener::onLocationChange error
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: nsIWebProgressListener::onLocationChange error
Confirmed. Should be innocuous, thought.
Will be fixed in next release.
Will be fixed in next release.
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: nsIWebProgressListener::onLocationChange error
Fixed in latest development build
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Re: nsIWebProgressListener::onLocationChange error
Big thanks for the fix.
I noticed the error in the Firebug console before I upgraded to Firefox 3.6. Indeed to get rid of this error information I decided not to wait till all my extensions were updated. And same as before.
Finally I managed to find here the solution. So I don't have to wait for the official release. THX.
Anna
I noticed the error in the Firebug console before I upgraded to Firefox 3.6. Indeed to get rid of this error information I decided not to wait till all my extensions were updated. And same as before.
Finally I managed to find here the solution. So I don't have to wait for the official release. THX.
Anna
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6