New issue
Advanced search Search tips

Issue 807847 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Opening zip archive triggers new Files window and subsequent zip files cause error display

Project Member Reported by mkarkada@chromium.org, Feb 1 2018

Issue description

Chrome OS Version: 10176.65.0, 64.0.3282.134 beta-channel on eve device

What steps will reproduce the problem?
(1) Open a ZIP file from Files app.
(2) Zip file is opened in new Files window.
(3) In this new Files window, open another zip file.
(4) In the original Files window, open another zip file.

What is the expected result?
Step (2) Zip file should be mounted in the same Files window.
Everytime opening a zip file should not trigger opening a new Files window.

What happens instead?
Step (2) Zip file should not be mounted in new Files window.
Step (3) Observed an error message dialog as 'This file is not supported...'. Please refer the screenshot.
Step (4) Again, opening a zip file triggers new Files window.

This issue not observed on latest M65 build.
 
Screenshot 2018-01-31 at 6.02.42 PM.png
307 KB View Download
Owner: yamaguchi@chromium.org
Status: Assigned (was: Untriaged)
Quick note - Is this a regression from M63 to M64?

Note: If we are not seeing this in M65, we should probably close as a WontFix.
Cc: mkarkada@chromium.org
Mergedinto: 797854
Status: Duplicate (was: Assigned)
I guess this is same issue as Issue 797854 which is recently fixed in M65, based on the report.
If that was the case, there would have been an incognito browser window when the problem was seen.
That is not a recent regression but existed since the ZIP unpacker extension was introduced.
Mergedinto: -797854 800543
I had a wrong Issue number. It's Issue 800543 (Files> Opening subsequent zip files in incognito mode cause error message display).
Status: Assigned (was: Duplicate)
Hi @Yamaguchi, this issue probably looks same as Issue 800543 but both are different because I'm not opening any incognito browser window in this case. I guess the fix should be merged to M64 as I am not seeing this issue on M65. 
Cc: yamaguchi@chromium.org
Owner: weifangsun@chromium.org
Should we give this up because it's too late for cherrypicking to M64?

This looks a new type of issue which we are not aware of. So this requires further investigation in order to do cherrypick.

Does this reproduce always, or on some limited deivces?
Status: WontFix (was: Assigned)
Yes - I am going to close as Won't Fix as we are not seeing this behavior in M65+.
Unable to reproduce this issue on M64 stable channel. Tested on eve, daisy, elm and hana devices.

Sign in to add a comment