Forwarding this message I sent to the mozilla-embedding mailing list 
that didn't get propogated to the group for some reason.



Hi all,

I have just checked in a new version of the web browser persist object and the associated nsIWebBrowserPersist interface. If you are using this interface in your client to save documents or URIs you will have to update your code. The key interface changes to note are:
  • saveCurrentURI() is gone. Call saveURI() instead, passing nsnull for the URI. Note this only works for the implementation of this interface on the web browser object.
  • nsIWebBrowserPersistProgress is gone. If you want to receive progress notifications implement nsIWebProgressListener, setting progressListener attribute on the interface to point at your listener.
  • New method cancelSave(). Call this to abort (but not clean up any files for) a download in progress.
  • New currentState attribute. Poll this to see if the implementation is busy or not.
  • New persistFlags attribute. Set flags to modify how URI data is saved, e.g. from cache or from the network.
  • New result attribute. Stores the result of the save operation to test for success or not.
Another important change is now the web browser persist object is a registered XPCOM object so it can be created and used from anywhere. Hopefully it will receive a much wider audience with this change.

This check-in is covered by bug 77909. Please raise new bugs if you run into problems or broken behaviour.

http://bugzilla.mozilla.org/show_bug.cgi?id=77909

Bug 99642 covers nsIWebBrowserPersist and it's suitability to be frozen as part of the embedding API freeze. It is possible that this process will cause the interface to be changed further, but hopefully just in minor ways.

http://bugzilla.mozilla.org/show_bug.cgi?id=99642

Adam


Reply via email to