Created attachment 8502824 [details] ss.txt Description: After stopping and resuming a download, the total file size has changed to what the download was stopped at Repro Steps: 1) Update a Flame to 20141008000201 2) Download a file 3) Stopped file in the download list 4) Tap yes > Tap the refresh icon 5) Try try again, download will appear failed 6) Tap the refresh icon > Try try again Actual: the total file size has changed Expected: the total file size does not changed Environmental Variables: Device: Flame 2.1 KK (319mb) (Full Flash) Build ID: 20141008000201 Gaia: d71f8804d7229f4b354259d5d8543c25b4796064 Gecko: 7fa82c9acdf2 Version: 34.0a2 Flame 2.1 KK (319mb) Firmware Version: v180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/case/13556/ See attached: screenshot, logcat
This issue also reproduce on the Flame 2.2 KitKat Base (319mb) and the Flame 2.0 KitKat Base (319mb)(Full Flash), the total file size has changed to what the download was stopped at Device: Flame 2.2 Master KK (319mb) (Full Flash) BuildID: 20141008040203 Gaia: 0bc74ce502672cf0265b24cf3a25d117c3de5e71 Gecko: e4cfacb76830 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 35.0a1 (2.2 Master) Firmware: v180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Device: Flame 2.0 KK (319mb) (Full Flash) BuildID: 20141008000202 Gaia: 31a49c7932c7085961760a6bef9ed381ea38d7e3 Gecko: a2d707e79061 Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf Version: 32.0 (2.0) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Not nominating to block on this issue. The user will see the correct file size when the download is first started, but the total size will change once the user pauses the download. But this does not corrupt the download.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.