Closed
Bug 717431
Opened 12 years ago
Closed 12 years ago
"No updates available" shouldn't change back to "Check for updates"
Categories
(Firefox for Android Graveyard :: General, defect, P4)
Tracking
(fennec+)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
fennec | + | --- |
People
(Reporter: mkohler, Unassigned)
References
Details
Attachments
(1 file)
1016 bytes,
patch
|
Details | Diff | Splinter Review |
"No updates available" shouldn't change back to "Check for updates" since the "About" window in desktop Firefox doesn't do it either.
Updated•12 years ago
|
Group: core-security
Reporter | ||
Comment 1•12 years ago
|
||
Attachment #589312 -
Flags: review?(mark.finkle)
Comment 2•12 years ago
|
||
Honestly, I kinda like being able to check again. Asking UX for final say though. Madhava - what say you?
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #2) > Honestly, I kinda like being able to check again. Asking UX for final say > though. > > Madhava - what say you? I think just reloading the page isn't such a PITA. We could also link the "No updates available" to checkForUpdates() instead, but I'm not quite sure if that is any improvement UX wise.
Comment 5•12 years ago
|
||
Why wouldn't we let people check again? This is mostly a developer tool - I'm not sure I worry too much about people getting confused and tapping it again and again, which I'd think is the only reason to shut it down for a while.
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 6•12 years ago
|
||
I mean, that said -- I'm honestly curious -- why do you think we shouldn't do this?
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: WONTFIX → ---
Reporter | ||
Comment 7•12 years ago
|
||
(In reply to Madhava Enros [:madhava] from comment #6) > I mean, that said -- I'm honestly curious -- why do you think we shouldn't > do this? I think it's better to make sure that the user has enough information. If you need to check again, a page reload is enough to display the button in its initial state. Adding the checkForUpdates function to "No updates available" could fix both problems (information and recheck). Would that be better?
Reporter | ||
Comment 8•12 years ago
|
||
Madhava?
Comment 9•12 years ago
|
||
The problem this bug is when the update server takes more than a second or two to reply and you look away from the phone. If you know the behavior well then yes you can infer that if there is no notice in the notification bar then there was no update. If you don't then you are left in an unknown state.
Comment 10•12 years ago
|
||
Like Kevin says: it just says "no update available" for a second, then goes back to the original. I think the comment #7 solution is a good one. (I can confirm this still happens on current Aurora.) Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA thought : Would people know to reclick on "No Update Available" to recheck if they don't read this bug? I believe it wouldn't be obvious and people will end up filing a bug on that itself because it doesn't say check for updates. Perhaps we can lengthen the time that it states "no update available"?
Reporter | ||
Comment 13•12 years ago
|
||
Any decision yet?
Reporter | ||
Updated•12 years ago
|
Assignee: michaelkohler → nobody
Comment 14•12 years ago
|
||
We are considering reworking the updater as a separate service in Android
Updated•12 years ago
|
Attachment #589312 -
Flags: review?(mark.finkle)
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•