Closed Bug 693714 Opened 8 years ago Closed 8 years ago
Bootstrapped addons have uninstall & install called on Firefox update
On first startup for Firefox 7 updating from Firefox 6, my addon's uninstall method is called immediately followed by it's install method. This is rather unfortunate and unexpected as my addon resets a pref on uninstall and sets a default value on install. This value can be customized by users so people are losing those custom values and blaming my addon (and creating custom versions with different defaults hardcoded & uploading those to third party sites so they'll never update).
Paul foolishly claimed he might want to take a look at this. Unassign if you change your mind.
Assignee: nobody → paul
Foolishly indeed. I'm not feeling well equipped to dig into this. The AOM code looks nice, but there's a lot of it and somebody more familiar with it should be better to jump in. I may look at this in the future if it's still open.
Assignee: paul → nobody
Hernan, not sure if you have other bugs to work on, but I thought this might be in the realm of things you could look at on a more limited schedule if you're interested.
Note to whomever works on this: Happens when DB schema changes.
Assignee: nobody → geoff
Status: NEW → ASSIGNED
OS: Mac OS X → All
Hardware: x86 → All
Attachment #567956 - Flags: review?(bmcbride) → review?(dtownsend)
Comment on attachment 567956 [details] [diff] [review] patch Review of attachment 567956 [details] [diff] [review]: ----------------------------------------------------------------- Excellent
Attachment #567956 - Flags: review?(dtownsend) → review+
The patch fails to apply.
Comment on attachment 568915 [details] [diff] [review] patch v2 The unbitrotting here has slightly changes the effect of the patch. I'd switch the if statements there back to what they were before I simplified them
The patch still doesn't apply on mozilla-inbound.
(In reply to Dão Gottwald [:dao] from comment #11) > The patch still doesn't apply on mozilla-inbound. Mossop is determined to bitrot me!
Attachment #568921 - Attachment is obsolete: true
Has this been sent to try, or do I need to do so before pushing? Just slightly wary after the mozilla-beta landings/backouts in the other bug ;-)
Target Milestone: --- → mozilla10
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.