Use previous target path when resuming a download after crash

content/browser/download/download_item_impl.cc

Index: content/browser/download/download_item_impl.cc
diff --git a/content/browser/download/download_item_impl.cc b/content/browser/download/download_item_impl.cc
index 9f9eae57ca69e1e02ec65b9d807bf6ec1965e1ab..cb96e3805867223859a3b1656dedee4abf177e49 100644
--- a/content/browser/download/download_item_impl.cc
+++ b/content/browser/download/download_item_impl.cc
@@ -627,6 +627,12 @@ const base::FilePath& DownloadItemImpl::GetForcedFilePath() const {
   return forced_file_path_;
 }
 
+base::FilePath DownloadItemImpl::GetLastUsedTargetPath() const {

[asanka, 2017/01/10 19:34:19]

Is there a case where GetTargetFilePath() and GetForcedFilePath() differ?

The only one I can think of is where the download gets destroyed or the devices
crashes during the initial download target determination. IMHO, if things go
south that close to the download initiation, it's much safer to discard the
intermediate file and start from the beginning. Before the first download target
determination, it's not accurate to refer to the value of GetForcedFilePath() as
the last used target path.

Let's get rid of this method if there is no other use case for it.

[qinmin, 2017/01/10 22:06:29]

Done.

+  if (GetForcedFilePath().empty())
+    return GetTargetFilePath();
+  return GetForcedFilePath();
+}
+
 base::FilePath DownloadItemImpl::GetFileNameToReportUser() const {
   if (!display_name_.empty())
     return display_name_;