New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 677425 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Context Menu in Files App is still seen even on clicking Uber Tray

Project Member Reported by mmanchala@chromium.org, Dec 29 2016

Issue description

Chrome Version: 57.0.2965.0/9130.0.0 dev-channel Kip,Peppy and Daisy
OS: Chrome

What steps will reproduce the problem?
(1)Sign into User -> Now go to Files App 
(2)Now open context menu using Two finger tap -> Now click on Uber Tray and observe context menu remains(Please refer Video)

Expected: On clicking Uber Tray Context Menu should get closed
Actual: Instead Context Menu is still seen even on clicking Uber Tray

This is a Regression issue as same is working fine in 53.0.2785.154/8530.96.2 Stable-Channel Daisy.
Issue not applicable to Linux and windows

@fukino :  Please confirm the issue
 
Actual_Menu.webm
504 KB View Download
Expected.mp4
3.6 MB View Download
Cc: sdantul...@chromium.org abod...@chromium.org rookrishna@chromium.org

Comment 2 by fukino@chromium.org, Jan 11 2017

Cc: osh...@chromium.org
This behavior starts from https://codereview.chromium.org/2330403002

From the CL, Files app window stays active by opening system tray, that's why the context menu in the Files app window is not closed.
Though this might be WAI, it is not consistent with the context menu of Chrome browser.

oshima@, is there a way for Chrome app to know the timing when system tray pops up?
Before, the window got inactive and blur event was dispatched to window object. We use the blur event to close the custom-made context menu.

Comment 3 by fukino@chromium.org, Jan 19 2017

Labels: -ReleaseBlock-Stable
Let me assign this to oshima@ who is the owner of the CL mentioned in c#2.

oshima@ san, could you mark this WontFix if it is WAI, or assign this back to me if we can avoid this behavior change.

BTW, I don't think this should block the release, as it is not the new regression of M57 and the issue does not look serious.
Removing RB label for now.

Comment 4 by fukino@chromium.org, Jan 19 2017

Cc: -osh...@chromium.org fukino@chromium.org
Owner: osh...@chromium.org

Comment 5 by osh...@chromium.org, Jan 20 2017

Status: WontFix (was: Assigned)
This is WAI. You have the same behavior when you open the context menu on desktop/launcher.

Sign in to add a comment