Closed Bug 612034 Opened 15 years ago Closed 8 years ago

no progress bar and messages when manually checking for updates

Categories

(Toolkit :: Add-ons Manager, defect)

defect
Not set
minor

Tracking

()

RESOLVED WONTFIX
Tracking Status
blocking2.0 --- -

People

(Reporter: al_9x, Unassigned)

Details

(Keywords: uiwanted)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7 3.6 has both with many add-ons, this could be a lengthy operation, so ui feedback is needed. in addition to printing the add-on name, as in 3.6, the host name would be useful, to see where it's getting stuck Reproducible: Always
Component: Download Manager → Add-ons Manager
QA Contact: download.manager → add-ons.manager
You mean the status at the left side of the utility button?
OS: Windows XP → All
Hardware: x86 → All
Version: unspecified → Trunk
(In reply to comment #1) > You mean the status at the left side of the utility button? Where they should be placed is a separate question, left of the button is reasonable since it already has the static status text "updating add-ons," but the main point is that they are absent. If it's not clear what I am referring to, do a manual update check in 3.6. During the checking, at the top of the add-on manager window, there is a spinner, progress bar, progress messages ("finished checking for updates to <extension>")
Not sure if this could be part of 4.0 due to necessary string changes. But I would like to get feedback from Jennifer. Confirming for now.
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Ever confirmed: true
Keywords: uiwanted
Not going to block 4.0. Any progress messages wouldn't really be useful since we no longer serially check each extension one after the other, instead we do them in parallel meaning that results come in randomly but often after about the same amount of time which would lead to a jerky progress bar which you can't really draw any conclusions from. We flag errors during the update check about specific add-ons in the error console but the majority of errors are out of the users' hands so it doesn't make much sense to expose it to them in primary UI.
blocking2.0: ? → -
(In reply to comment #4) > Not going to block 4.0. > > Any progress messages wouldn't really be useful since we no longer serially > check each extension one after the other, instead we do them in parallel > meaning that results come in randomly but often after about the same amount of > time which would lead to a jerky progress bar which you can't really draw any > conclusions from. We flag errors during the update check about specific add-ons > in the error console but the majority of errors are out of the users' hands so > it doesn't make much sense to expose it to them in primary UI. We actually checked them in parallel previously which is why the ui reported when a checked finished vs. a check started.
given comment 4 and comment 5, is it safe to say that this is no longer relevant to the current UI, that a patch would not be approved if provided?
Severity: normal → minor
Flags: needinfo?(amckay)
Probably safe to assume, but I confess I've no idea what UI is being talked about in this bug. Marking as won't fix as a result. If anyone knows where this, a screenshot would help. Thanks for checking on this Wayne.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(amckay)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.