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

Issue 748946 link

Starred by 13 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Desktop: Installed (windowed) apps, Chrome should not intercept keyboard shortcuts

Project Member Reported by mgiuca@chromium.org, Jul 26 2017

Issue description

Chrome Version: 61
OS: Windows, Mac, Linux, Chrome OS

What steps will reproduce the problem?
(1) Install an app (Menu -> More tools -> Add to desktop/shelf)
(2) Run the app from the shortcut (should open in a window)
(3) Press Ctrl+T, Ctrl+N, Ctrl+W.

What is the expected result?
Shortcut not captured by browser. App has access to those shortcuts.

What happens instead?
The usual browser behaviour (new tab, new window, close window) respectively.

This should alleviate some concerns in  Issue 680809  (it would not work in a tab, but if the user installs your app, those shortcuts become available).
 
Just FYI, I think Ctrl + T is a system level shortcut for ChromeOS (pls confirm), so we should preserve the behavior there as a fallback, unless it's overridden by the app.
c#1: That is the intention - default functionality will remain as it currently is unless the app specifically adds a keyDown listener for that combination.
Cc: benwells@chromium.org
I think this fits into the area of windowing behavior. It would be good to get an umbrella bug for all the things like that.
Cc: tbuck...@chromium.org
Owner: ovanieva@chromium.org
Status: Assigned (was: Available)
To ovanieva to decide the correct behavior.
Components: UI>Browser>AppShortcuts
Owner: dominickn@chromium.org
I think we've already decided the right behaviour here, this is just awaiting implementation.
Components: UI>Browser>WebAppInstalls
Status: WontFix (was: Assigned)
As it turns out, this behaviour is already implemented, as "app-mode" Browsers don't reserve any keys, and installed apps are treated as being in "app-mode" by virtue of having Browser::app_name set to the extension ID of the bookmark app.

It also seems to work with fullscreen: pressing Esc while in fullscreen exits fullscreen, even if you capture Esc. This means you can't get stuck in fullscreen, which is good.

Sign in to add a comment