Closed Bug 737598 Opened 8 years ago Closed 7 years ago
Tracking: Prompts and interaction for gecko updates
In the initial landing of bug 737368, updates will be automatically applied no matter what the user is doing. A slight improvement on this is showing the user a prompt that asks whether it's OK to update now, or wait a little bit. Kinda like what windows does for high-priority security updates. If the user isn't around, the update goes through. An improvement on top of that would be to only kick off an update off a long idle timer. And of course, in any model, we need to notify applications that they're being killed so that they can save persistent state. This is mostly covered by other bugs though.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #0) > An improvement on top of that would be to only kick off an update off a long > idle timer. > (But still ask the user confirm/deny, I should have added.)
8 years ago
8 years ago
Depends on: 740722
blocking-basecamp: --- → +
blocking-kilimanjaro: --- → +
Fabrice, if you're not the owner of this, please re-assign. cjones, does this cover both the backend work and the Gaia work?
Assignee: nobody → fabrice
I think it's a dupe of Bug 740720 (also relevant here : bug 737601 and bug 746754). So jstraus is the natural owner, unless he wants to unassign himself and I'll take them.
The idea was to track the progression of that work here, but closing this bug is fine with me.
There are some messy inter-dependencies here so let's make this bug a meta bug and re-assign it to nobody. Thanks.
Assignee: fabrice → nobody
Summary: Let users cancel a pending auto-update → [meta] Let users cancel a pending auto-update
Please nom the individual bugs, tracking a meta bug as a blocker doesn't sound like a good plan.
Updating this tracking bug to track any/all prompt and UX work for gecko updates
OS: Linux → Gonk
Hardware: x86_64 → ARM
Summary: [meta] Let users cancel a pending auto-update → Tracking: Prompts and interaction for gecko updates
Should this depend on Bug 785124 and Bug 781233? Otherwise should we resolve this since all dependencies are done?
Closing based on comment #8. (I'm hoping there's nothing I'm supposed to add other than RESOLVED FIXED but sorry if I am)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.