When loading the frameset document in the URL, the throbber never stops.

mscott, it doesn't look like the nsIWebProgressListener::OnStatusChange (flag_net_stop) is being called in this case.

Travis, that's because it's a child doc loader that finishes the load so the stop is coming back via a OnChildStatusChange instead of a onStatusChange. Maybe that's bogus on my part and I should always call onStatusChange...

Fixed. I always call OnStatusChange for starting and stopping a document instead of using the onChildStatusChange even if a child was the one who signaled the on stop document load.

Yeah, the point is you should be able to watch just OnStatusChange and you will only be told when the top level doc starts and stops as well as the transition points for the top document in the middle. If you don't care about the actual status of individual frames loading then you can ignore OnChildStatusChange. So basically in a frame world you should get.. OnStatusChange(flag_net_start) OnStatusChange(flag_net_dns) OnStatusChange(flag_net_connecting) OnStatusChange(flag_net_negotiating) Possibly...OnStatusChange(flag_net_redirecting) OnStatusChange(flag_net_transferring) OnChildStatusChange(flag_net_start) [frame 1] ... Other dns, connecting etc for the given frame OnChildStatusChange(flag_net_stop) OnChildStatusChange(flag_net_start) [frame 2] ... Other dns, connecting etc for the given frame OnChildStatusChange(flag_net_stop) OnStatusChange(flag_net_stop) Obviously the child status messages may intermix, but basically it's an encapsulation of starts and stops.

Oh, looks like you already fixed it. :)

Fixed in the May 22nd build.