Issue metadata
Sign in to add a comment
|
Saving file to read-only folder looks like it succeeds (but fails) |
||||||||||||||||||||||||
Issue descriptionChrome 52.0.2729.3 OSX 10.11.5 What steps will reproduce the problem? (1) Create a folder named "test" (2) chmod -w test (3) Download a file from Chrome to "test". (4) Click on the error and "Show in Finder" What is the expected output? If Chrome can't download the file, Chrome shows some indicator that the download failed. At last in step 4. What do you see instead? The download shows a progress circle and flashes blue circles, just as if the download was successful. Step 4 has no effect, with no explanation. (And, of course, nothing shows up in the folder "test".) If you visit chrome://downloads, the file is detected as gone. It shows up in chrome://downloads as "Deleted", and at this time the Downloads bar updates to show it as "Removed" (why the inconsistent terminology?). As a strawman, would it be easy to do the removal detection at the end of the download, and show the file as "Removed" instead of flashing as if the download were successful?
,
May 23 2016
The behavior you describe is clearly not what should happen. However I can't reproduce the issue following your instructions. At step 3 the download fails with "Insufficient permissions." This is the correct behavior. Clicking "Resume" also correctly displays the file chooser since the download target path is no longer considered valid. I'm trying this on a ToT build. Could you try this out again on a tiny download and capture a net-internals log while doing so? I've attached a small file to this comment for your convenience. The log will contain any file system level errors that were seen during the course of the download. Instructions at https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details .
,
May 27 2016
,
May 27 2016
,
Jun 4 2016
So, it turns out that I can repro this only with *page downloads*, not file downloads. "Webpage, Complete" and "Webpage, HTML Only" both exhibit the problem. Downloading a JPEG file, however, results in "Failed - Insufficient permis..." on the Downloads bar. In case it helps, here's a net-log of trying to download the first page you see (sign-in page) on a fresh Chrome profile.
,
Jun 17 2016
Ah yes. SavePackage is notorious for not dealing with interruptions correctly. It has a lot of historical baggage that we are working on. Now that the downloads resumption work is easing off, I'll work on fixing these issues. Merging this issue to the oldest one I could find that mentions the shortcomings of SavePackage error handling. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ellyjo...@chromium.org
, May 20 2016Status: Assigned (was: Untriaged)