Issue metadata
Sign in to add a comment
|
ChromeOS issue: Regression: .ica and .cr file are opened with text editor since M-63 |
||||||||||||||||||||
Issue descriptionChromeOS version: 63.0.3239.140 ChromeOS device model: any Case#: 14696022 Steps to reproduce: What steps will reproduce the problem? 1. Install application which has a file handler for "text" for "ica" and "cr" extensions (Citrix Receiver haiffjcadagjlijoggckpgfnoeiflnem) 2. Double click an .ica file to open it. 3. The file is opened with text editor since M-63, but not in M-62 What is the expected output? What do you see instead? .ica should not to be opened with text editor, but with Citrix Receiver. Yuki, can you please help to fix/triage?
,
Jan 22 2018
yamaguchi@, please correct me if I'm wrong about the current implementation. After we add Text app as a default application, I assume this is an expected behavior. I guess followings happen: 1) Text app can open *.ica file, since its mime type can be sniffed as text. 2) Citrix Receiver is installed, but haven't been opened from Files app. 3) In this situation, Text app is treated as a default app for the file, since default built-in app is prioritized over unused third-party apps. If Citrix Receiver is chosen from OPEN dropdown menu in Files app, it will be respected after that. That said, I think matching of file extension should be prioritized than matching of mime type. In this case, Text app matches the ica file by mime type (text/plain) and Citrix Receiver matches the ica file by file extension. Unless the user explicitly choose the default app, Citrix Receiver should be prioritized. +weifangsun@ to confirm the expected behavior.
,
Jan 22 2018
I think it will not, but only after user explicitly chooses the app by "change default" menu, with the existing logic. https://bugs.chromium.org/p/chromium/issues/detail?id=751950#c9 https://cs.chromium.org/chromium/src/chrome/browser/chromeos/file_manager/file_tasks.cc?q=file:file_tasks.cc&sq=package:chromium&dr&l=629 It gives higher priority to the built-in apps than other non-generic handlers.
,
Jan 24 2018
OK. Then this is the expected behavior at this moment. Let's consider respecting file extension more than mime type in M66.
,
Feb 7 2018
,
Feb 16 2018
<files-triage>
,
Feb 28 2018
,
Feb 28 2018
,
Feb 28 2018
,
Apr 19 2018
,
Jul 19
,
Oct 23
,
Jan 11
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time. - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Jan 14
This bug is still in my queue as part of MIME (and file extension) related work, next steps haven't been identified yet.
,
Jan 14
Thanks for the update. Is there any sort of estimate on when this may be addressed?
,
Jan 15
Still working out priorities for fixing. This is related to the more general MIME handling bug https://bugs.chromium.org/p/chromium/issues/detail?id=848124 Will update when I have a better idea of an estimate. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by yawano@chromium.org
, Jan 22 2018Owner: fukino@chromium.org