Closed
Bug 830463
Opened 13 years ago
Closed 13 years ago
download/update notification is showing up late on a weak connection in some cases
Categories
(Core Graveyard :: DOM: Apps, defect)
Tracking
(firefox19 wontfix, firefox20 wontfix, firefox21 fixed, b2g18+ fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)
RESOLVED
FIXED
mozilla21
People
(Reporter: jsmith, Assigned: julienw)
References
Details
Attachments
(1 file, 1 obsolete file)
|
7.49 KB,
patch
|
julienw
:
review+
lsblakk
:
approval-mozilla-b2g18+
|
Details | Diff | Splinter Review |
Related to bug 830447.
Build: B2G 18 1/14/2013
Device: Unagi
Steps:
1. Install a hosted app preloading appcache on a weak connection (Mozilla Guest) after trying an install once before in bug 830447
Expected:
Upon downloading starts, we should show a download progress for the appcache hosted app being downloaded.
Actual:
On a weak connection, a noticeable delay can be seen before the download notification shows up. Definitely not a blocker cause progress is evident eventually, but this does feel a tad awkward?
| Reporter | ||
Updated•13 years ago
|
Blocks: app-install
See Also: → 830447
| Assignee | ||
Comment 1•13 years ago
|
||
| Assignee | ||
Comment 2•13 years ago
|
||
ie we can't do anything here because we don't get any event from the platform before the first progress.
| Assignee | ||
Comment 3•13 years ago
|
||
I got an idea discussing with Michal.
I believe that if gecko sends a progress event (with app.progress === 0) as soon as the download start, then gaia would display the notification ASAP.
This is imho the best solution as no solutions in gaia can cover all cases now, eg the "launch the update download from the app" case (because if gaia doesn't initiate the download, it doesn't know about it before the first progress), and the "restart a failed install" case (because we don't have an event for the resume, and therefore gaia only knows at the first progress).
I could work on a patch for this but first I'd like Fabrice's feedback.
Component: Gaia::System → DOM: Apps
Flags: needinfo?(fabrice)
Product: Boot2Gecko → Core
Summary: Installing a hosted app preloading appcache on 2nd try - download notification is showing up late on a weak connection → download/update notification is showing up late on a weak connection in some cases
| Assignee | ||
Updated•13 years ago
|
Assignee: nobody → felash
| Assignee | ||
Comment 5•13 years ago
|
||
tested both install and update cases for both packaged and hosted+appcache apps, in both a strong and weak connection (far from my wifi router).
This works fine for me.
Attachment #712250 -
Flags: review?(fabrice)
| Assignee | ||
Updated•13 years ago
|
tracking-b2g18:
--- → ?
Comment 7•13 years ago
|
||
Comment on attachment 712250 [details] [diff] [review]
patch v1
Review of attachment 712250 [details] [diff] [review]:
-----------------------------------------------------------------
::: dom/apps/src/Webapps.jsm
@@ +2825,5 @@
> " - " + aApp.installState);
> this.app = aApp;
> this.startStatus = aApp.installState;
> this.lastProgressTime = 0;
> + // send a first progress event to correctly set the external object's
nit: s/external/DOM
Attachment #712250 -
Flags: review?(fabrice) → review+
| Assignee | ||
Comment 8•13 years ago
|
||
fixed nits, carrying r=fabrice
Attachment #712250 -
Attachment is obsolete: true
Attachment #712364 -
Flags: review+
| Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
| Assignee | ||
Comment 9•13 years ago
|
||
Comment on attachment 712364 [details] [diff] [review]
patch v2
[Approval Request Comment]
Bug caused by (feature/regressing bug #): -
User impact if declined: the primary bug is that the notification is showing late when downloading (installing/updating) on weak connection (that is: in our target market). Bug this triggers things like Bug 839715, that are especially important if we're not uplifting Bug 838561.
Testing completed: yes, I tested virtually all code paths modified by this patch. Of course we could wait that this lands in central and that Jason tests this before upliting. Or we can uplift this and test the resulting build.
Risk to taking this patch (and alternatives if risky): very low as we're not modifying any logic here, but merely sending an already existing event.
String or UUID changes made by this patch: none
I believe we need either this or fix in Bug 838561, without one of them the user can put the phone in a strange state that would need a reboot to recover correctly. I also believe this fix is safer (no change in the branching and the code path, contrary to fix in Bug 838561).
So I'd really want to see this in v1.0.
Attachment #712364 -
Flags: approval-mozilla-b2g18?
Comment 10•13 years ago
|
||
Keywords: checkin-needed
Comment 11•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Updated•13 years ago
|
Comment 12•13 years ago
|
||
Comment on attachment 712364 [details] [diff] [review]
patch v2
Approving this lower risk option, bug Bug 838561 is being held for approval until we're landing to v1.1
Attachment #712364 -
Flags: approval-mozilla-b2g18? → approval-mozilla-b2g18+
Comment 13•13 years ago
|
||
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•