Agreed this is a bad experience. On my device, the screen goes to Chrome and I get the typical downloading confirmation and notification, which even if we are using CCT we should be doing. We will take a look.

Yeah even if we have a notification and/or toast, showing a blank page seems like a pretty bad user experience.  It isn't clear what the user is supposed to do.  

+shaktisahu@ for any dev work that pops up.  E.g. do we want to automatically open the download here?  That's a better experience than the current flow, but if we show a actionable UI instead of a blank page it might not be necessary.

+yusufo@ for FYI since he owns CCT.

Jon do you think we could show some more relevant UI here instead of just a blank page?  Maybe if we can't think of anything else, we can bump them to Download Home where they can see the download progressing.  IIUC we aren't rendering any page content here anyway because the initial CCT WebContents navigation was stolen for a download.

The min bar intended behavior is that the user should see the downloading snackbar and the downloading notification. 

*If* we can reliably detect the case where the CCT is blank, then we have three options:
-Showing the downloads home so the user can track the download and open the file once it is done
-Keeping a blank page, but opening the PDF using the default intent handler when the file has successfully downloaded
-Returning to the original context/app the spawned the CCT (this is similar to how a normal download would behave on a page. 

All of these would be better than what we are doing today, but which one is best will take a bit more analysis. Can we go ahead and fix the snackbar/notification problem now and put the second part on my backlog? 

Sure.  Reassigning to shaktisahu@.  Marking as M-61 for now.

Actually, I am seeing the download snackbar here in 62.0.3164.0
Attached video. However the page stays until I press back arrow to dismiss.

Deleted: xyz.mp4 2.2 MB

	xyz.mp4 2.2 MB View Download

Ok so our existing flow seems to work.  It's sad that we hide the snackbar after a timeout and have no way to do anything with the CCT once the download is done.

We should make this better IMO.  Even if the behavior is currently expected it doesn't feel like a good experience.

Before moving on, I think we should diagnose why mdw@ isn't seeing the download notification and snackbar. Matt, were you on a particularly slow network? Sometimes it takes significant time for the download to start.

Or as an alternative reason, the snackbar dismisses after a certain period of time (5-10 seconds?).  Do you think maybe you missed seeing it?

I was using M61, not M62. However, even the flow shown in #5 is suboptimal in my opinion - you're stuck looking at a blank page for the duration of the download, and see a blank page after the download is complete (and the snackbar disappears).

Agreed it is suboptimal. However, I wanted to first assess whether there was a regression that we needed to fix ASAP. If you are seeing the notification and snackbar then we can change the priority and milestone of this.

Also, I noticed if you have very old versions of chrome installed on the device, that might cause the issue that mdw@ experienced. I also had a M55 on my device where I saw no snackbar at all. Once I disabled that version, I was able to see the snackbar.

:( can't fix 55, but +qinmin@ in case he has any idea when the snackbar logic was added.