Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060902 BonEcho/2.0b2 The behavior is visible for me since I'm using Nightly Tester Tools with current 1.8 branch builds. When I open Talkback over the extensions main menu entry I have to enable Talkback every time when Firefox or Thunderbird was updated. If an update is applied Talkback shouldn't be deactivated. Instead we should check its state and apply it to the new Firefox/Thunderbird version. And activating it every day is by the way a hassle.
I just tried reproducing unsuccessfully by installing 2.0b1 on a fat partition and then using software update to upgrade to 2.0b2. I did a fresh install of beta 1 and received a partial update. I installed on a fat partition because I thought this may be due to bug 346407. Can you try reproducing without NTT? NTT and Mr. Tech Local Install both write directly to the extensions datasource which may be the cause of this for you.
Also, NTT has an option to "Disable compatibility overwriting during application update" that I highly suspect would cause this. This isn't the only reason it could cause this but it is the most likely.
(In reply to comment #2) > Also, NTT has an option to "Disable compatibility overwriting during > application update" that I highly suspect would cause this. This isn't the only > reason it could cause this but it is the most likely. Ok, you are right. After disabling NTT Talkback stays enabled after an automatic update. If NTT is enabled I have to check this option and then it also stays enabled. Does this happen to any incompatibility of the Talkback extension or do we have the fault in NTT?
From what I can see this only happens with NTT though I suspect MTLI will do the same thing since it uses the code from NTT to provide the functionality provided by NTT.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
I've contacted the extensions author because that issue. v.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.