Closed Bug 1478053 Opened 6 years ago Closed 6 years ago

Download progress notification can't be dismissed after closing app

Categories

(Firefox for Android Graveyard :: General, defect, P1)

Unspecified
Android
defect

Tracking

(geckoview62 unaffected, firefox-esr52 unaffected, firefox-esr60 unaffected, firefox61 unaffected, firefox62+ wontfix, firefox63+ wontfix, firefox64 verified)

VERIFIED FIXED
Firefox 64
Tracking Status
geckoview62 --- unaffected
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox61 --- unaffected
firefox62 + wontfix
firefox63 + wontfix
firefox64 --- verified

People

(Reporter: andrei.a.lazar, Assigned: vlad.baicu)

References

Details

(Keywords: regression, Whiteboard: [priority:high])

Attachments

(1 file)

Steps to reproduce:
1) Go to https://www.thinkbroadband.com/download
2) Start downloading something
3) Close the application before the download is finished
4) Try to interrupt the download by using the Cancel action within the notification

Expected result:
The download will stop and the notification will disappear

Actual result:
Nothing happens
Whiteboard: [priority:high]
Most of the patches in the regression range are DOM/CSS/l10n/JS engine patches, I see a necko patch in that range that might look more likely to produce such a regression. Jan, do you think that your patch in bug 1442178 could have caused this regression?
Flags: needinfo?(odvarko)
(In reply to Pascal Chevrel:pascalc from comment #2)
> Most of the patches in the regression range are DOM/CSS/l10n/JS engine
> patches, I see a necko patch in that range that might look more likely to
> produce such a regression. Jan, do you think that your patch in bug 1442178
> could have caused this regression?

Bug 1442178 has been fixed by Jan Bambas (:mayhemer).
I can't forward NI to him atm (he's on PTO), so I pinged him through email.

Honza
Flags: needinfo?(odvarko)
Jason, do you have more info on this?

Honza
Flags: needinfo?(jduell.mcbugs)
Assignee: andrei.a.lazar → nobody
(In reply to Jan Honza Odvarko [:Honza] from comment #3)
> (In reply to Pascal Chevrel:pascalc from comment #2)
> > Most of the patches in the regression range are DOM/CSS/l10n/JS engine
> > patches, I see a necko patch in that range that might look more likely to
> > produce such a regression. Jan, do you think that your patch in bug 1442178
> > could have caused this regression?
> 
> Bug 1442178 has been fixed by Jan Bambas (:mayhemer).
> I can't forward NI to him atm (he's on PTO), so I pinged him through email.
> 
> Honza

Hard to say if this is related.  Logs [1] might help answer this.

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
Flags: needinfo?(jduell.mcbugs)
Andrei: What device and API are you using? Would a logcat help?
Flags: needinfo?(andrei.a.lazar)
Hei Marcia, this is reproducible on any device that is at least API 26, though, I am not pretty sure what is the expected result. Should the download stop when closing the app from background?
Flags: needinfo?(andrei.a.lazar) → needinfo?(mozillamarcia.knous)
adding Paolo in case he knows the answer to Comment 7. I am not sure what the expected behavior is for either desktop or android for download manager.
Flags: needinfo?(mozillamarcia.knous) → needinfo?(paolo.mozmail)
For Desktop, downloads are cancelled when closing the application, but we show a quit confirmation dialog box.

I don't know what is the expected behavior on Android. When we are running in multi-process mode, our internal download state and progress notifications are handled in the parent process, so if this process terminates then downloads have to stop as well.
Flags: needinfo?(paolo.mozmail)
Andreas, does product have any opinions on expected behavior here?
Flags: needinfo?(abovens)
When trying this in Chrome, the download continues in the background (and can be tracked via the built-in Download manager). We should probably do the same.
Flags: needinfo?(abovens)
Susheel, could you prioritize this regression? Should it be fixed and uplifted for 63? Thanks
Flags: needinfo?(sdaswani)
Vlad can you work on this ASAP?
Flags: needinfo?(sdaswani) → needinfo?(vlad.baicu)
Assignee: nobody → vlad.baicu
Flags: needinfo?(vlad.baicu)
Setting priority P1 because Susheel asked Vlad to work on this bug ASAP (in comment 13).

Could this bug affect GeckoView in Focus?
Priority: -- → P1
Summary: Progress notification is broken after closing app → Download progress notification can't be dismissed after closing app
Persistent notifications were not properly distinguished from clearable notifications
because they would first start as not persistent and got updated afterwards. Also added
a handle action in BrowserApp's onCreate for whenever the process gets removed.
Comment on attachment 9011878 [details]
Bug 1478053 - Remove persistent notifs from the clearable list. r=sdaswani

Jim Chen [:jchen] [:darchons] has approved the revision.
Attachment #9011878 - Flags: review+
Keywords: checkin-needed
Pushed by ebalazs@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/55660b661412
Remove persistent notifs from the clearable list. r=jchen
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/55660b661412
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 64
See Also: → 1495443
Tested with 
- Xiaomi Mi4i(Android 5.0.2), 
- Nokia 6(Android 7.1.1) and after the browser is closed, the notification is not displayed. Is displayed again and the files are downloaded if I re-open the browser. 
Nightly build 64.0a1 (2018/01/10) downloaded from Google Play. 

For some devices: Nexus 5(Android 6.0.1), Motorola Nexus 6(Android 7.1.1), HTC Desire 820 (Android 6.0.1), Google Pixel (Android 9) the issue is not fixed and filed bug 1495443.
Vlad, could you request beta uplift please? thanks
Flags: needinfo?(vlad.baicu)
Not sure if this issue is ready for a beta uplift because it appears there are still some isssues left to sort out regarding this functionality, signaled in bug 1495443 and bug 1495743.
Flags: needinfo?(vlad.baicu)
Since bug 1495443 is stalled for now and we are in our last week of betas, this is wontfix for 63.

Verified as fixed on Firefox 64.0.2.

Status: RESOLVED → VERIFIED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: