Google Drive "Add to" files & directories don't show up in the local ChromeOS files app.
Reported by
da...@xyzzy.com.au,
Jan 28 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10032.86.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.140 Safari/537.36 Platform: 10032.86.0 (Official Build) stable-channel edgar Steps to reproduce the problem: 1. Create directories "originals" & "copies" in the root directory using the Google Drive web interface. 2. Put some files in the "originals" directory. 3. In the Google Drive web interface, select the "originals" directory, and press "Shift + Z". Select "Add to" (NOT "Move to"), and put the "originals" directory inside the "copies" directory. i.e. The Google Drive equivalent of a Symlink of a directory etc. What is the expected behavior? Using the ChromeOS files app, you should now see the "Originals" directory in it's old location (e.g. "Google Drive -> My Drive") AND under the "copies" directory in the ChromeOS files application under "Google Drive -> My Drive -> copies". What went wrong? When viewed with the native ChromeOS files app, the directory (and/or files) do not show up. They should be visible. File system view via the files app is inconsistent with the web interface view. Note: It performs correctly on the Google Drive web interface. i.e. Like a Unix symlink. Note: "Move to" works as expected. Did this work before? No Chrome version: 63.0.3239.140 Channel: stable OS Version: 10032.86.0 Flash Version: 28.0.0.137
,
Feb 20 2018
<files-triage>
,
Feb 20 2018
,
Feb 28 2018
,
Mar 28 2018
Revisit once drive update is complete.
,
Apr 19 2018
,
Oct 31
Fixed by moving to DriveFS. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by treib@chromium.org
, Feb 19 2018