Ctrl+Tab doesn't work after notification |
||||||
Issue description
Chrome Version : 57.0.2987.133
OS Version: Goobuntu Trusty
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Get event notification from Google Calendar
2. Press "Enter" to dismiss
3. Ctrl+Tab or Ctrl+Shift+Tab to switch tabs
What is the expected result?
Current tab changes according to keyboard commands
What happens instead of that?
Current tab remains on Calendar
Please provide any additional information below. Attach a screenshot if
possible.
Either manually changing tabs or switching to another window and back restores Alt+Tab functionality.
Manually creating a dialog using (e.g.) alert() doesn't reproduce this.
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
,
Apr 8 2017
Notifications: Allow (by policy). What do you mean by "alerts rather than notifications"? I've been using those terms to mean that GCalendar creates a "notification" for an event, which (I am assuming) is rendered via a call to window.alert().
,
Apr 24 2017
Does http://output.jsbin.com/mijefe work as expected re popping an alert from a background page?
,
Apr 24 2017
It works as expected, i.e. hitting Enter, or clicking on "OK", dismisses the alert dialog, and then Ctrl+Tab cycles through tabs as expected.
,
Apr 25 2017
I cannot reproduce this, and like the other bug I am at a total loss. What version of the OS are you using? In chrome://versions, what variations do you have?
,
Apr 25 2017
Google Chrome 57.0.2987.133 (Official Build) unknown (64-bit) Revision ec33cd0c06881d919ac0de419d829ad914e0be8f-refs/branch-heads/2987@{#887} OS Linux JavaScript V8 5.7.492.71 Flash 25.0.0.148 /usr/local/google/home/mdavis/.config/google-chrome/PepperFlash/25.0.0.148/libpepflashplayer.so User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Command Line /opt/google/chrome/chrome --profile-directory=Default --disable-gpu --flag-switches-begin --flag-switches-end Executable Path /opt/google/chrome/chrome Profile Path /usr/local/google/home/mdavis/.config/google-chrome/Default Variations 3ac60855-3ec2a267 f296190c-9e248081 4442aae2-7158671e ed1d377-e1cc0f14 75f0f0a0-6bdfffe7 e2b18481-6e3b1976 e7e71889-4ad60575
,
Apr 26 2017
My peeps, in the other bug people reported that they were on the old dialogs. Can you folks try with the new-style alerts? Try launching Chrome with the commandline: --enable-features=AutoDismissingDialogs and let me know how it goes.
,
Apr 28 2017
Tom, tagging you as owner so it doesn't get lost.
,
Apr 28 2017
Confirmed: enabling AutoDismissingDialogs fixes this issue (and the other one as well).
,
May 1 2017
I am going to be turning AutoDismissingDialogs to 100% deployment. Thomas, I'm leaving in the disabling switch for as long as it takes for you to work through this bug and issue 709685. Let me know when you're done.
,
May 12 2017
,
May 12 2017
,
Jul 20 2017
,
Jul 20
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by a...@chromium.org
, Apr 8 2017