nsIWebProgressListener.onProgressChange: first argument is null

UNCONFIRMED
Unassigned

Status

()

Toolkit
General
UNCONFIRMED
6 years ago
4 years ago

People

(Reporter: Simon Stewart, Unassigned)

Tracking

1.9.2 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
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.
(Reporter)

Updated

6 years ago
Hardware: x86_64 → x86
The browser status filter dispatches some onProgressChange events that are not associated with any particular webprogress instance.

Updated

4 years ago
Component: General → JavaScript Engine
Product: Firefox → Core
Version: 3.6 Branch → 1.9.2 Branch

Updated

4 years ago
Component: JavaScript Engine → General
Product: Core → Toolkit
You need to log in before you can comment on or make changes to this bug.