Closed
Bug 299700
Opened 19 years ago
Closed 19 years ago
Automatically check for updates for "my extensions and themes" is unchecked after checking manually
Categories
(Firefox :: Settings UI, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: BlindWolf8, Assigned: bugs)
References
Details
(Whiteboard: ETA: 7/29)
Attachments
(1 obsolete file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050704 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050704 Firefox/1.0+ Whenever I check for updates to my extensions and themes manually, the checkbox to autocheck for updates to my extensions and themes is automatically unchecked. Even though I sometimes like to check for updates manually doesn't mean I would like to check manually _all_ the time.... Zip build Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050704 Firefox/1.0+ ID:2005070405 Reproducible: Always Steps to Reproduce: 1. Open up DPa1 2. Go to Tools -> Options -> Advanced -> Update 3. Check the box labeled "My Extensions and Themes" 4. Click the "Check Now..." button under the aforementioned checkbox 5. Click the "Finish" or "Cancel" buttons to exit the update window (doesn't matter if it's done checking or not) 6. Notice that now the "My Extensions and Themes" checkbox is unchecked. Expected Results: The autoupdate extensions and themes checkbox should have remained checked (FF 1.0.4 does this perfectly).
| Reporter | ||
Updated•19 years ago
|
Flags: blocking1.8b3?
Comment 1•19 years ago
|
||
its a bug, yes, but not something we'll hold 1.8b3 for at the last minute...
| Reporter | ||
Comment 2•19 years ago
|
||
As a side note, this ONLY happens when you do a "Check Now..." in PrefWindow V. This does NOT happen when you are in the Extensions manager and right-click an extension and choose to check for updates for that extension. So this seems to confirm that it is a problem in PrefWindow V.
Flags: blocking1.8b4?
Flags: blocking1.8b3?
Flags: blocking-aviary1.1?
Comment 3•19 years ago
|
||
sounds like its the exact same problem that happened with the app update thing.
Flags: blocking1.8b3?
| Reporter | ||
Comment 4•19 years ago
|
||
Mike Conner said that this bug will not block 1.8b3.
Flags: blocking1.8b3?
Updated•19 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•19 years ago
|
Assignee: nobody → beng
Flags: blocking1.8b4?
Flags: blocking1.8b4+
Flags: blocking-aviary1.1?
Comment 6•19 years ago
|
||
Previously, the preference attribute was set on the button (which I saw is NOT set on the DP check now button). Removing the attribute fixes this bug for me. Seems to be the correct way to me.
Attachment #189494 -
Flags: review?(mconnor)
| Assignee | ||
Comment 7•19 years ago
|
||
This is not the right fix, I don't think. We were using this preference as a way to control the disabled state of this button based on the lockedness of the autoUpdateEnabled pref. Perhaps, instead, there should be a separate disable_buttons preference to do this. Either way, this patch removes functionality.
Whiteboard: SWAG: 1d
Comment 8•19 years ago
|
||
Comment on attachment 189494 [details] [diff] [review] patch Didn't see the locked pref thing. Thanks. Two questions though: 1) Will bug 296566 have any impact on this? 2) Will a small js hack be appropriate to keep the checkbox checked?
Attachment #189494 -
Attachment is obsolete: true
Attachment #189494 -
Flags: review?(mconnor)
Comment 9•19 years ago
|
||
(In reply to comment #7) > This is not the right fix, I don't think. We were using this preference as a way > to control the disabled state of this button based on the lockedness of the > autoUpdateEnabled pref. Perhaps, instead, there should be a separate > disable_buttons preference to do this. Either way, this patch removes > functionality. I am not sure I understand what you are saying. Is the intent here to prevent an automatic check for extension update to fire during a manual chaeck?
Updated•19 years ago
|
Assignee: beng → bugs
| Assignee | ||
Updated•19 years ago
|
Whiteboard: SWAG: 1d → ETA: 7/29
| Assignee | ||
Comment 12•19 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•