Closed Bug 1553200 Opened 6 years ago Closed 6 years ago

Fix nsIWebProgressListeners registered on RemoteWebProgressManager with missing event handlers

Categories

(Core :: DOM: Content Processes, enhancement)

68 Branch
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: beth, Assigned: beth)

References

Details

Attachments

(1 file, 4 obsolete files)

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 but ideally we should be registering our nsIWebProgressListeners with the correct flags so that this error is not hit.

Assignee: nobody → brennie
Status: NEW → ASSIGNED
Attachment #9070325 - Attachment is obsolete: true
Attachment #9070324 - Attachment is obsolete: true
Attachment #9070326 - Attachment is obsolete: true
Attachment #9070322 - Attachment is obsolete: true
Keywords: leave-open
Keywords: leave-open

I think all other usages were cleaned up as part of other bugs as the only remaining usage of addProgressListener without a flag are on gBrowser.

Pushed by brennie@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/910ee59da71c Do not receive unwanted nsIWebProgress events in addon discovery view r=mconley
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: