Hi, the advertised way to transition into extensions that provide a secure update path does not appear to work in FF3.0b4.
I implemented secure updates using spock, and tested this implementation. It works fine, both in FF2.0 and FF3.0b4, if I manually go to Tools -> Add-On -> Check for updates. However, when I start FF3.0b4 for the first time, the following happens: FF3.0b4 detects that the installed extension is non-compliant; offers to check for updates (why, btw, does the user have to click here? Previous FF updates, to my knowledge, checked unprompted.) I check for updates, it finds an update, I install it, the installation appears to succeed, however, when I restart FF3.0b4, the extension is still disabled. [ If I subsequently go to Tools->Add-Ons and check for updates, it'll find the update, install it, and reactivate it on the following restart. ] Clearly, this is not uninterrupted service. I'm wondering if I am doing something wrong - has anybody else tested this important scenario and found it to work? Thanks! - Godmar [1] For those who want to test it: http://libx.org/editions/5C/FB/5CFB7B98.1/libx-5CFB7B98.xpi (this is a build of libx.mozdev.org code, see libx.org) _______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
