inconsistent drag vs. double-click behavior in Files app |
|||||||||
Issue description(This may be multiple bugs---feel free to split.) On my chromebook, if I drag an extension-less file from the Files app to an empty tab, the file is opened as text. But if click on it, I get the message "this file type is not supported". If the file ends in .txt, both actions have the desired effect. If the file ends with an unknown suffix, for instance .log, double-clicking invites me to pick an extension that can deal with that file type (which I don't really want to do). Dragging the file into a tab navigates to about:blank. My workaround is to rename files to .txt. But if the file is mounted from opening a ZIP archive, first I have to copy it. I am not sure how comparable this is, but on my Linux desktop, visiting an extension-less file URL opens the file as text, which is my preference anyway.
,
Feb 23 2018
It seems like we attempted to support type-sniffing files at one point. I filed issue 126863 long ago, which got duped into issue 352250 , which was marked fixed in 2014. Comment #33 there indicates that we attempt to handle plain-text files. Maybe it regressed, or I'm misunderstanding. I also frequently need to extract log files from archives and add .txt extensions before I can double-click them to open them in a tab.
,
Feb 24 2018
,
Feb 28 2018
,
Feb 28 2018
,
Mar 12 2018
Observed in 67.0.3365.0: Double click: txtfile | prompt: file type not supported txtfile.log | prompt: file type not supported txtfile.txt | open in new tab test.zip:txtfile | prompt: file type not supported test.zip:txtfile.log | prompt: file type not supported test.zip:txtfile.txt | open in new tab Drag into tab: txtfile | open txtfile.log | open txtfile.txt | open test.zip:txtfile | about:blank test.zip:txtfile.log | about:blank test.zip:txtfile.txt | about:blank
,
Mar 15 2018
,
Mar 15 2018
,
Oct 23
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by semenzato@chromium.org
, Feb 23 2018