Closed Bug 314208 Opened 19 years ago Closed 19 years ago

'Check for Updates...' doesn't check for extension updates

Categories

(Firefox Graveyard :: Help Documentation, defect)

1.5.0.x Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 2

People

(Reporter: steffen.wilberg, Assigned: steffen.wilberg)

References

()

Details

(Keywords: fixed1.8.1, verified1.8.0.1)

Attachments

(1 file, 2 obsolete files)

"Check for Updates..." only checks for app updates, but not extension updates.
Just watch the JS Console when you click "Find Updates" EM; that doesn't happen when you select "Check for Updates".
Attached patch patch (obsolete) — Splinter Review
Also explains the process of downloading and installing an update by restarting Firefox. Also explains the various labels of the menuitem (except Resume Downlading), see http://lxr.mozilla.org/mozilla1.8/source/browser/base/content/utilityOverlay.js#501
Assignee: nobody → steffen.wilberg
Status: NEW → ASSIGNED
Attachment #201241 - Flags: review?(jwalden+fxhelp)
Comment on attachment 201241 [details] [diff] [review]
patch

>+  <p>Displays a dialog which checks for updates to &brandShortName; and asks
>+    you whether you want to download available updates. After an update has been

This seems to be biased toward there typically being available updates, but in release versions this will be the exception (versus the behavior to which we've become accustomed in nightlies).  I think changing "available updates" to "updates if any are available" would ameliorate this problem.

>+    downloaded, it asks you to restart &brandShortName; so that the update can

"it" is a vague term here.  I know you're trying to refer to the updater itself, but there's no difference between the application and the updater to the user.  I'm not sure what's the best way to resolve this.

>+    be installed. While an update is being downloaded, this menu item is
>+    labelled "Downloading &brandShortName; (version)...". If an update is ready
>+    to be installed and &brandShortName; is waiting for you to restart it, this
>+    menu item is labelled "Apply Downloaded Updates Now...".</p>

I'm not convinced that enumerating the different labels for the menu item is a good idea; I think it's more a waste of space than a genuine help to the user.  Perhaps mentioning, "This menu item's name will change while an update is being downloaded and installed." might do the trick, but I'm not entirely sure.
Attachment #201241 - Flags: review?(jwalden+fxhelp) → review-
Attached patch patch v1.1 (obsolete) — Splinter Review
> I think changing "available updates" to
> "updates if any are available" would ameliorate this problem.
Fixed.

> >+    downloaded, it asks you to restart &brandShortName;
> 
> "it" is a vague term here.  I know you're trying to refer to the updater
> itself, but there's no difference between the application and the updater to
> the user.  I'm not sure what's the best way to resolve this.
Of course it's all Firefox, but I meant a certain little part of it which is the the update dialog, which asks you to restart now or later, so I replaced "it" with "the dialog".

> Perhaps mentioning, "This menu item's name will change while an update is being
> downloaded and installed." might do the trick, but I'm not entirely sure.
How about "The name of this menu item will change when an update is being downloaded or ready to be installed."?
Attachment #201241 - Attachment is obsolete: true
Attachment #201963 - Flags: review?(jwalden+fxhelp)
Comment on attachment 201963 [details] [diff] [review]
patch v1.1

(In reply to comment #3)
> How about "The name of this menu item will change when an update is being
> downloaded or ready to be installed."?

Put an "is" before "ready to be installed" and start the sentence with "Note that" (because it feels more like an aside than an integral part of the menu item's docs but doesn't really deserve the space a full "Note: ..." paragraph would give it) and r=me.

To the approver: this is a simple fix to make our documentation of one menu item a little more accurate; Firefox currently doesn't check for updates to extensions when Tools > Check for Updates... is invoked (tho it once did), so we'd like to fix it.
Attachment #201963 - Flags: review?(jwalden+fxhelp)
Attachment #201963 - Flags: review+
Attachment #201963 - Flags: approval1.8rc2?
Comment on attachment 201963 [details] [diff] [review]
patch v1.1

In the past we've been flexible in approving help only changes. I don't think we can approve changes to the help viewer for the branch anymore because we believe we have final bits in hand and don't plan on respinning. 

So we'd never see this change anyway.
Attachment #201963 - Flags: approval1.8rc2? → approval1.8rc2-
Attached patch patch v1.2Splinter Review
Review comments addressed.
Attachment #201963 - Attachment is obsolete: true
Attachment #202553 - Flags: review+
Trunk checkin:
Checking in mozilla/browser/locales/en-US/chrome/help/menu_reference.xhtml;
/cvsroot/mozilla/browser/locales/en-US/chrome/help/menu_reference.xhtml,v  <--  menu_reference.xhtml
new revision: 1.36; previous revision: 1.35
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox1.6-
Attachment #202553 - Flags: approval1.8.0.1?
*** Bug 317525 has been marked as a duplicate of this bug. ***
Comment on attachment 202553 [details] [diff] [review]
patch v1.2

Please land on 1.8 and 1.8.1 branches.
Attachment #202553 - Flags: approval1.8.1+
Attachment #202553 - Flags: approval1.8.0.1?
Attachment #202553 - Flags: approval1.8.0.1+
Checked into 1.8 and 1.8.0 branches.
verified on mac, build 2006010904
verified on mac, build 2006011103 (a 1.8.0.1 build)
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: