TB 60.9.1 automatically updates toTB 72 on opening.
Categories
(Thunderbird :: Disability Access, defect)
Tracking
(Not tracked)
People
(Reporter: erwinm, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:56.0) Gecko/20100101 Firefox/56.0 Waterfox/56.3
Steps to reproduce:
I opened ÞB earlier today. It auto-updated to 68.3.1, breaking accessibility fixes and making ÞB unusable. I installed ÞB 60.9.1 over 68.3.1 to try to get ÞB working, since I need working email.
Actual results:
ÞB 60.9.1 auto-updated to ÞB 72.0b2, which is just as broken as 68.3.1.
Expected results:
There needs to be some way to create and keep a usable ÞB installation without it auto-updating to an unusable one.
P.S. Disconnected from internet, reinstalled, set to "never check for updates," reconnected, seems to be working for now.
However, given the problems involved with dropping to earlier versions, and with not using security updates, maybe these would help:
-
NOT breaking accessibility fixes with these updates, and
-
NOT hijacking "check for updates, but let me choose whether to install them" to auto-update without any choice.
|
||
Comment 2•4 years ago
|
||
What accessibility problems do you see?
We've got positive feedback from multiple visually impaired people about the accessibility state in 68.
60.9.1 should be updating to 68.3.1, and apparently you got that too. I don't understand how you got to 72.0b2.
I'm not sure how that happened either. css changes broke existing userChrome.css fixes to (a) make the folder list readable and (b) block the animated sticky alerts about blocking remote content. See bug 1606013. (please use the word "bug" in front of bug numbers)
|
||
Comment 4•4 years ago
|
||
(In reply to MarjaE from comment #1)
P.S. Disconnected from internet, reinstalled, set to "never check for updates," reconnected, seems to be working for now.
However, given the problems involved with dropping to earlier versions, and with not using security updates, maybe these would help:
- NOT breaking accessibility fixes with these updates, and
This is of course bug 1606013 which you have mentioned. a) and b) mentioned in comment 3 I believe you have filed bugs about?
- NOT hijacking "check for updates, but let me choose whether to install them" to auto-update without any choice.
This is covered by an existing bug#.
So this bug can be closed as there is nothing actionable here? This appears to be a duplicate of Bug 160013, except filed under a different and incorrect component.
Description
•