Could not create a file in Google Drive folder on CrOS with a frontslash. Works fine on web then in CrOS shows as an underscore |
||||||
Issue descriptionChrome Version : 54.0.2840.93 OS Version: 8743.83.0 What steps will reproduce the problem? 1. Open Files 2. Open Google Drive Folder 3. Two finger click and select New Folder 4. Name the folder with a frontslash What is the expected result? I am able to create the folder, and it shows properly named What happens instead of that? I receive an invalid character error. Please provide any additional information below. Attach a screenshot if possible. If I go to drive.google.com and create the folder, it works fine, but Files then shows what was the frontslash as an underscore. UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 8743.83.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.93 Safari/537.36
,
Jan 28 2017
Fukino-san. Is this a known issue?
,
Jan 30 2017
IIUC it is a know restriction. We disallow some characters (including '/') for file/folder names for technical reasons. If Google Drive files already have such characters, we replace those characters to display them in Files app. +hashimoto@, please correct me if I'm wrong.
,
Jan 30 2017
Correct. IIRC this behavior is compatible with Drive clients on other platforms.
,
Jan 30 2017
Other platforms support this just fine, I humbly request you reconsider this.
,
Feb 24 2018
Assigning to weifang, please advise as to whether we should support this.
,
Feb 26 2018
> Other platforms support this just fine, I humbly request you reconsider this. Chrome OS's path handling is based on that of Linux and '/' works as a path separator, so '/' cannot appear in file names. IIUC Drive sync clients on other platforms (i.e. Win, Mac, and Linux) do the same thing. Could you kindly enlighten me how "other platforms support this just fine"?
,
Feb 26 2018
For example, on Mac, I can create a folder named "Test/Test" and it syncs fine to Google Drive, and doesn't replace the slash with an underscore. '/' can appear just fine in folder names on Mac.
,
Feb 27 2018
You are seeing slashes in file names on Finder because it's replacing colons with slashes when displaying file names. You'll see colons instead of slashes when using Terminal which displays the real file name. IMO we shouldn't replicate Mac's behavior which results in creating a new problem about file names which contain colons.
,
Feb 27 2018
But on Web, I see a slash, not a colon for the folder created on Mac...
,
Feb 27 2018
Google Drive allows users to create a file whose name contains slashes (IMHO this is not a good design decision), but when the file is downloaded to a computer, on all supported platforms those slashes will be replaced with another character. Closing as WAI. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rohi...@chromium.org
, Jan 28 2017