New issue
Advanced search Search tips

Issue 841782 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 22
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

[MacViews-Browser] Block interaction with keyboard shortcut, when a Menu is open

Project Member Reported by meh...@chromium.org, May 10 2018

Issue description

Chrome Version: Latest Canary 68
OS: macOS 10.13.4

What steps will reproduce the problem?
(0) Enable MacViews-Browser
(1) Open two tabs
(2) In the second tab click on a Bookmarks Folder, so that the Menu appears or make a right-click on the Bookmarks Bar so that the context menu appears
(3) Press CMD-W to close the Tab (or press CMD-T to open a new tab)

What is the expected result?
CMD-* should be blocked.

What happens instead?
CMD-* is not blocked.

Not sure if this is intended under MacViews. The problem is, that the Menu doesn't disappear when closing or opening a new Tab.

Thanks
Mehmet


 
menu_bug.mov
720 KB View Download
Owner: lgrey@chromium.org
Status: Assigned (was: Untriaged)
[mac bug triage] Assigning to lgrey to have a look
Labels: MacViews-Release
Owner: erikc...@chromium.org
Redirecting to erikchen@ for hotkeys.
Owner: bettes@chromium.org
This isn't technically related to hotkeys.

e.g. this can also be reproed with (3) Select "file->close tab" from the main menu.

That should absolutely work even if a context menu is showing.

Then the question is: should the context menu self-close? As a quick check, I confirmed that if the context menu is opened on the web page itself, then closing the tab closes the context menu.

In this case, the context menu is opened from the bookmarks bar, which is still present even after the previous tab is closed...I guess I think that this should continue to be the case [this seems like the natural behavior to me]. 

Note: In Cocoa, context menus prevent access to the main menu. e.g. clicking on the main menu will first dismiss the context menu [and not change the main menu], and a second click is required to open the main menu.

So it looks like the root difference between Cocoa and views is that in Cocoa, a context menu basically blocks all other UI interaction [including hotkeys, main menu access, etc.]

This looks like an intentional design design? Over to bettes.
Labels: -MacViews-Release
Labels: Group-Focus_Input_Selection_Activation_KeyState
Labels: Hotlist-DesktopUIChecked
** UI Mass Triage**

No issue seen on mac latest versions-72.0.3618.0. Adding labels for expert review.Please find attached screencast for reference.

841782-working on latest.mp4
613 KB View Download
Cc: jmukthavaram@chromium.org
Status: WontFix (was: Assigned)
Can not repro any longer. Closing.

Sign in to add a comment