693970 - nsIWebProgressListener.onProgressChange: first argument is null

Status: UNCONFIRMED

(Toolkit :: General, defect)

Description

[Simon Stewart]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.83 Safari/535.2

Steps to reproduce:

In JS, create a new nsIWebProgressListener. The onProgressChange method should be declared and check the first argument is not undefined or null.

Register the new listener via something like:

gbrowser.addProgressListener(listener, Components.interfaces.nsIWebProgress.NOTIFY_STATE_REQUEST | Components.interfaces.nsIWebProgress.NOTIFY_PROGRESS);


Actual results:

The first argument to onProgressChange is null.


Expected results:

The documentation indicates that the first argument to onProgressChange should be the nsIWebProgress that fires the event. This implies that it will always be set.

Comment 1

[Boris Zbarsky [:bzbarsky]]

The browser status filter dispatches some onProgressChange events that are not associated with any particular webprogress instance.