Office Editing for Docs, Sheets & Slides has errors when opening files that have a space in the filename
Reported by
cst...@mcfarlandclinic.com,
May 1 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: 1. Install the Office Editing for Docs, Sheets & Slides extension 2. Set Chrome.exe as the default for opening .docx, .xlsx, etc. files 3. Double-click a .docx file with a space in the name, such as "Test File.docx" What is the expected behavior? Double-clicking a .docx file with no space in the name opens the file in Chrome correctly. ex "TestFile.docx" instead of "Test File.docx" What went wrong? Files with spaces in the name cause a ERR_FILE_NOT_FOUND error, and open a new tab for every word separated by a space in the filename. see attached WebStore page: https://chrome.google.com/webstore/detail/office-editing-for-docs-s/gbkeegbaiigmenfmjfclcdgdpimamgkj/reviews?hl=en Did this work before? N/A Chrome version: 66.0.3359.117 Channel: stable OS Version: 10.0 Flash Version:
,
May 9 2018
Unable to reproduce this issue on Windows 10 with chrome #66.0.3359.117 ; #66.0.3359.139 as per steps mentioned in comment #0 Attaching the screen-cast for reference. cstole@ Could you please look into this issue and re-try the scenario on clean profile with no apps & extensions and let us know your observations.
,
May 9 2018
I tested the files again using a new user profile with only the Office Editing for Docs Sheets and Slides Chrome extension installed. The "TestDocx.docx" (no space in filename) file opens in Chrome correctly. The "Test Docx.docx" (space in filename) still produces an ERR_FILE_NOT_FOUND error, and opens a new tab for every word separated by a space in the filename. We are using Windows 10 v1703 15063.1029. The behavior is also reproducible on Windows 7 computers.
,
May 9 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 14 2018
I don't think that this is related only to managed Chrome. Removing the Enterprise component.
,
May 18 2018
Unable to reproduce this issue on reported version and latest stable using Windows 10 with steps mentioned in comment#0 and comment#3. Seeing same output as in comment#2. Attaching screenshots for reference. @Reporter: Please check the screenshots and let us know if we miss anything. Please provide a screencast which reproduces the issue. Thanks!
,
Jun 4 2018
,
Jun 4 2018
I remember seeing a bug a few months ago around the handling of quoted strings on the command line on windows, but I can't seem to find it at the moment. It's possible this has been fixed by the change there. Given #6, let's tentatively call this fixed and re-open if anyone can still reproduce. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mheinsohn@chromium.org
, May 1 2018