Bug 1553200 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Bug 1547806 mentioned running into the following error in the browser console:

>RemoteWebProgress failed to call onStatusChange: [Exception... "JavaScript component does not have a method named: "onStatusChange"'JavaScript component does not have a method named: "onStatusChange"' when calling method: [nsIWebProgressListener::onStatusChange]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "JS frame :: resource://gre/modules/RemoteWebProgress.jsm :: _callProgressListeners :: line 103" data: no]

This error is [handled gracefully](https://searchfox.org/mozilla-central/source/toolkit/modules/RemoteWebProgress.jsm#105) but ideally we should be registering our nsIWebProgressListeners with the correct flags so that this error is not hit.
Bug 1547806 mentioned running into the following error in the browser console:

>RemoteWebProgress failed to call onStatusChange: [Exception... "JavaScript component does not have a method named: "onStatusChange"'JavaScript component does not have a method named: "onStatusChange"' when calling method: [nsIWebProgressListener::onStatusChange]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "JS frame :: resource://gre/modules/RemoteWebProgress.jsm :: _callProgressListeners :: line 103" data: no]

This error is [handled gracefully](https://searchfox.org/mozilla-central/rev/9eb2f739c165b4e294929f7b99fbb4d90f8a396b/toolkit/modules/RemoteWebProgress.jsm#102) but ideally we should be registering our nsIWebProgressListeners with the correct flags so that this error is not hit.

Back to Bug 1553200 Comment 0