Closed Bug 32229 Opened 25 years ago Closed 25 years ago

nsIDocumentLoaderObserver not firing on reload

Categories

(Core :: Layout, defect, P1)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dougt, Assigned: travis)

References

Details

I have implemented a nsIDocumentLoaderObserver to perform actions related to the security icon and alerts. I have found that during a Refresh, or going back in my history, OnStartURLLoad and OnStopURLLoad are not firing.
Blocks: 30322
Travis, is this your bug?
Priority: P3 → P1
Target Milestone: M15
Actually, this bug will probably go away when the webprogress interfaces are added and he changes his code to watch those.
when will your new interfaces be live?
I need to make sure that this works in your new interface for both reloads, and history page transitions.
Move to M16 for now ...
Target Milestone: M15 → M16
this is a major problem! I need some kind of status on this before blindly moving to m16. Without this, someone can spoof a secure site.
Target Milestone: M16 → M15
Oh well, let them spoof away. This WILL NOT slow down M15. That's not what M15 is for. We will hold M16 for this obviously. Besides, Travis is at Internet World this week and I have no-one else to fix it. I want the tree opened back up on Friday for M16 or we'll never make May 2nd. Call me or send me email if this is a problem.
This is critically important that it gets fixed: the sooner the better. based on don's assertions --> m16.
Target Milestone: M15 → M16
nsIWebProgress Interfaces are actually sending information for starting and stopping of a load. The change of a location can also be seen with the OnLocationChange message.
what about url loads? This is what is not firing on the nsIDocuementLoader.
What do you mean an url load? What other type of load are we talking about?
there are two type of notifications that I need from the doc loader. The first notifications are for the Page: OnStartDocumentLoad and OnStopDocumentLoad. The second are for the indivudual URL loads on that page. I am interested in both.
Ok, so the nsIWebProgress Interfaces are actually notifying of the top level loads that are occuring. The child loads are I think wrong at this point. The toplevel change of location is right.
This is fixed. Marking as such.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking verified based on reporter's comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.