Diaa wrote: > Yes I did that and it worked properly, thanks much. > There's another problem I ran into which is that no progress bar is > displayed and FF is not aware about loading(even the Stop button is > disabled),
To have a working progress bar, you need to get an nsIProgressEventSink from your notification callbacks (and, if that fails, from the loadgroup's notification callbacks) and call onProgress/onStatus as needed. You also have to put the channel into the loadgroup in AsyncOpen, and remove it after calling OnStopRequest, but you seem to have figured that out. Unfortunately I don't have an idea on why the second channel would be created; the only reason I can think of is that you don't have a contentCharset and the data contains a <meta> element with charset info. That causes a new channel to be created and loaded, but that wouldn't happen right after asyncOpen... -- All the world's a stage, And all the men and women merely players: They have their exits and their entrances; And one man in his time plays many parts, [...] --W. Shakespeare _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
