Closed Bug 859586 Opened 8 years ago Closed 8 years ago

Remove {Start,End,Fail}DocumentLoad notifications


(Firefox :: Extension Compatibility, defect)

Not set



Firefox 23


(Reporter: billm, Assigned: billm)


(Blocks 1 open bug)


(Keywords: addon-compat, dev-doc-complete, Whiteboard: [e10s])


(1 file)

Attached patch patchSplinter Review
These aren't used within firefox. Felipe says that the addons that use them are no longer up-to-date. Also, the interface is weird because it only notifies you if the load happens in the foreground tab.
Attachment #734920 - Flags: review?(felipc)
Comment on attachment 734920 [details] [diff] [review]

as endDocumentLoad is gone, let's rename startDocumentLoad to something better (clearCurrentPageData maybe?) and remove the aRequest unused parameter (but don't remove it from the if condition that calls the function)
Attachment #734920 - Flags: review?(felipc) → review+
I see at least a couple of active add-ons that still use these notifications. That shouldn't stop you from fixing this, and I also agree that it's an odd API that has better alternatives.
Keywords: addon-compat
I did a search for amo addons that include the string |DocumentLoad"| (without the bars). I filtered out addons where maxversion was below FF4. I also filtered out Thunderbird addons, since I'm assuming that Thunderbird doesn't use code from browser.js (maybe I'm wrong?). I found only two addons:
I'm guessing this is now mostly used by SeaMonkey since Firefox already has a built-in DOM inspector. Does SeaMonkey use browser.js from Firefox?
Looks like people still use it, although it was last updated for FF9.

If nobody objects, I'm going to land this with Felipe's changes as well as a comment requested by Gavin.
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 23
Whiteboard: [e10s]
Blocks: fxe10s
As a follow up. Not all xpi are getting distributed via

I can confirm that hundreds of our addons were using EndDocumentLoad and this change breaks certain features in our framework.

We created a fix and we currently are rolling updates for our most important customers.

We found out the exact cause of this problem thanks to Jorge Villalobos and his post on 2013/07/24.
OS: Linux → All
Hardware: x86_64 → All
You need to log in before you can comment on or make changes to this bug.