Chrome Version       : Version 59.0.3071.115 (Official Build) (64-bit)
URL : www.chase.com
Behavior in Safari 4.x/5.x: ?
Behavior in Firefox 3.x/4.x: ?

What steps will reproduce the problem?
(1) Sign into an account on www.chase.com.  (I used a credit card account.)
(2) Click to download a statement.  Statement appears in Chrome's built-in PDF viewer.
(3) Click the download button in the PDF viewer and select a file name to save a local copy of the PDF.

Result:  Silent failure.  No local copy of the PDF is made.  User thinks they've saved their statement but they actually haven't.

It appears that clicking the button in the PDF viewer doesn't save the already-downloaded PDF file but instead attempts to download it again.  (Why?) That download fails, but there's no UI indication of this.

If you look in Chrome's download history (Ctrl+J), you'll see it listed as a failed download with a generic "Network Error".  Clicking the "Resume" button causes the error message to change to "Forbidden", which suggests chase.com doesn't like something about the second download request.  That might ultimately be a bug with the chase.com site, but, at a minimum, Chrome's PDF viewer needs to tell the user that something went wrong.

Problem began in late May or early June.  Before that, this flow worked fine.

Expected Result:

Best:  Copy the already-downloaded PDF to the user-selected file name.

Good:  Solve the network problem that prevents the second download attempt from working.

Acceptable:  Tell the user that the second download failed.  Otherwise, the user may think they have successfully saved a copy of their statement when they actually haven't.


Workaround:  None that I've found.  There no longer seems to be a way to make a local copy of the PDF.