Extensions blocking nsIDocShell on addProgressListener callbacks

RESOLVED INCOMPLETE

Status

()

Firefox
Extension Compatibility
RESOLVED INCOMPLETE
11 years ago
7 years ago

People

(Reporter: Effie Nadiv, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-11-15])

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

When one of those extensions is installed (Noscript, Google Browser Sync, Google Notebook, FlashGot, MediaPlayerConnectivity, Stumbleupon 2.89, Tab Mix Plus or Infolister) addProgressListener ceases to pass nsIDocShell to its callback functions. aRequest passed to the callback does not contain nsIDocShell in the notificationCallbacks even for root documents. 

Reproducible: Always

Steps to Reproduce:
1. Install Noscript, Google Browser Sync, Google Notebook, FlashGot, MediaPlayerConnectivity, Stumbleupon 2.89, Tab Mix Plus or Infolister
2. addProgressListener
3. Inspect aWebProgress passed to onStateChange



Disable the extensions (on the list) and aWebProgress returns to be a valid nsIDocShell (and notificationCallbacks returns to contain nsIDocShell)

Actual Results:  
aWebProgress is never nsIDocShell
aWebProgress.documentCharsetInfo is always null.
aRequest.notificationCallbacks never contains nsIDocShell

Expected Results:  
aWebProgress is nsIDocShell for root documents.
aWebProgress.documentCharsetInfo is nsIDocumentCharsetInfo for root documents.
aRequest.notificationCallbacks contains nsIDocShell

Once those extensions are disabled, Firefox returns to behave as expected.
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.