Chrome Version: 58.0.3029.89 (Official build)(64-bit)
Platform: stable channel gnawty
OS: Chrome OS
What steps will reproduce the problem?(1) Turn off flag(chrome://flags) for "Office Editing for Docs, Sheets & Slides".
(2) Open the attached html file(mimetypeAllEvents.html) in chrome browser.
(3) Drag and drop any macro-enabled file (.docm, .xlsm, .pptm)
What is the expected result?
Should print the correct mime-type of macro-enabled file.
What happens instead?
Prints empty string.
Additional Information:
(1) Open the attached html file(mimetype.html) in chrome browser. Open developer console.
(2) Drag and drop any docx file
(3) Check console for the message from Chrome. The console prints correct mime type for docx file. (Please refer msword-docx-mimetype.png)
(4) Now perform step 2 and 3 for docm file.
(5) The mime type for docm is printed as application/zip.(Please refer msword-docm-mimetype.png)
What is the expected result?
Should print the correct mime-type of macro-enabled file.
Chrome Version: 58.0.3029.89 (Official build)(64-bit)
Platform: stable channel gnawty
OS: Chrome OS
What steps will reproduce the problem?
(1) Turn off flag(chrome://flags) for "Office Editing for Docs, Sheets & Slides".
(2) Open the attached html file(mimetypeAllEvents.html) in chrome browser.
(3) Drag and drop any macro-enabled file (.docm, .xlsm, .pptm)
What is the expected result?
Should print the correct mime-type of macro-enabled file.
What happens instead?
Prints empty string.
What is the expected result?
Should print the correct mime-type of macro-enabled file.
Additional Information:
(1) Open the attached html file(mimetype.html) in chrome browser. Open developer console.
(2) Drag and drop any docx file
(3) Check console for the message from Chrome. The console prints correct mime type for docx file. (Please refer msword-docx-mimetype.png)
(4) Now perform step 2 and 3 for docm file.
(5) The mime type for docm is printed as application/zip.(Please refer msword-docm-mimetype.png)
Chrome Version: 58.0.3029.89 (Official build)(64-bit)
Platform: stable channel gnawty
OS: Chrome OS
What steps will reproduce the problem?
(1) Turn off flag(chrome://flags) for "Office Editing for Docs, Sheets & Slides".
(2) Open the attached html file(mimetypeAllEvents.html) in chrome browser.
(3) Drag and drop any macro-enabled file (.docm, .xlsm, .pptm)
What happens instead?
Prints empty string.
What is the expected result?
Should print the correct mime-type of macro-enabled file.
Additional Information:
(1) Open the attached html file(mimetype.html) in chrome browser. Open developer console.
(2) Drag and drop any docx file
(3) Check console for the message from Chrome. The console prints correct mime type for docx file. (Please refer msword-docx-mimetype.png)
(4) Now perform step 2 and 3 for docm file.
(5) The mime type for docm is printed as application/zip.(Please refer msword-docm-mimetype.png)
Chrome Version: 58.0.3029.89 (Official build)(64-bit)
Platform: stable channel gnawty
OS: Chrome OS
What steps will reproduce the problem?
(1) Turn off flag(chrome://flags) for "Office Editing for Docs, Sheets & Slides".
(2) Open the attached html file(mimetypeAllEvents.html) in chrome browser.
(3) Drag and drop any macro-enabled file (.docm, .xlsm, .pptm)
What is the expected result?
Should print the correct mime-type of macro-enabled file.
What happens instead?
Prints empty string.
Additional Information:
(1) Open the attached html file(mimetype.html) in chrome browser. Open developer console.
(2) Drag and drop any docx file
(3) Check console for the message from Chrome. The console prints correct mime type for docx file. (Please refer msword-docx-mimetype.png)
(4) Now perform step 2 and 3 for docm file.
(5) The mime type for docm is printed as application/zip.(Please refer msword-docm-mimetype.png)
What is the expected result?
Should print the correct mime-type of macro-enabled file.
Please Note: Same issue has been observed for microsoft template files. Chrome browser sends incorrect mime-type as 'application/zip' for 2k7(.dotx/.xltx/.potx) template files and 'application/octet-stream' for 2k3(.dot/.xlt/.pot) template files.
Extension-to-filetype mapping is OS- and even user-dependent, which is problematic in general. See:
https://github.com/w3c/FileAPI/issues/51 and issue 155455
... but on CrOS we are in control, so could populate the mapping?
Comment 1 by upasana....@synerzip.com
, May 22 2017