New issue
Advanced search Search tips

Issue 843902 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

New tab doesn't respond to keyboard after switching away from it immediately after opening

Reported by russell....@gmail.com, May 17 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. Search for "chromium bugs" on google
2. Click the first search result while holding Command and Shift (this will cause it to open in a new tab and switch to that tab)
3. Immediately press Ctrl-Tab to switch away from the new tab.
4. Wait for the new tab to finish loading, then switch back to it.

What is the expected behavior?
The tab responds to keyboard input like usual.

What went wrong?
Try using the arrow keys to scroll, or try pressing tab to move the keyboard focus. The tab doesn't respond to any keyboard input at all.

Did this work before? N/A 

Chrome version: 66.0.3359.181  Channel: stable
OS Version: OS X 10.13.4
Flash Version: 

The steps above reproduce the problem using only builtin functionality. A more realistic scenario (and how I discovered the bug), is to install an extension like https://chrome.google.com/webstore/detail/google-search-navigator/cohamjploocgoejdfanacfgkhjkhdkek, and open the new tab from the search results using the keyboard, then immediately switch back to the search results page using ctrl-shift-tab.

I also confirmed that the bug still occurs when switching away from the tab (step 3 above) using the mouse instead of the keyboard.
 
Labels: Needs-Feedback
Mac triage: I can't reproduce this with 66.0.3359.181 on 10.13.5 beta.

Reporter: how reliably do the repro steps given above work for you? I had zero successes in five attempts.

Could you attach a screencast of the problem? Quicktime player can make screen recordings.
Labels: Needs-Triage-M66
Weird, I can no longer reproduce by opening the link with the mouse as described in step 2. It's possible I was mistaken in seeing that behavior (though I really thought I did). Sorry about that.

Anyway, I can still reproduce (100% of the time) via the approach described in the last two paragraphs of my description above. I also have an even simpler way to reproduce:

1) Open the developer console.
2) Run window.open("https://bugs.chromium.org/p/chromium/issues/list")
3) Immediately switch back to the previous tab by pressing ctrl-shift-tab
4) Wait for the new tab to finish loading, then switch back to it

I've attached a screencast showing the problem.

chrome-bug.mp4
151 KB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, May 17 2018

Cc: ellyjo...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -ellyjo...@chromium.org
Labels: -Type-Bug -Pri-2 hasbisect-per-revision ReleaseBlock-Stable Triaged-ET M-66 FoundIn-66 Target-66 Pri-1 Type-Bug-Regression
Owner: ellyjo...@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on reported version 66.0.3359.181 and the same is not seen on latest chrome 68.0.3433.0 and Beta 67.0.3396.48 using  Mac 10.12.6, hence providing reverse bisect info
Note: Issue is not seen on Windows 10 & Ubuntu 14.04
Reverse Bisect Info:
================
Last Bad build: 67.0.3378.0
First Good build: 67.0.3379.0

You are probably looking for a change made after 545257 (known good), but no later than 545258 (first known bad).
https://chromium.googlesource.com/chromium/src/+log/0ace60f0bda35d4788e12314314758465ccf70f5..e09df9251bdc1f717aa76df1629a04143971a15e
Reviewed-on: https://chromium-review.googlesource.com/969078

@Elly Fong-Jones: Please confirm the issue and help in re-assigning if it is not related to your change, please help in merging it to M-66 if applicable
Adding ReleaseBlock-Stable for M-66, feel free to remove it if not applicable.

Thanks!
Friendly ping to get an update on this issue as it is marked as M66 stable blocker.

Thanks..!
Gentle ping to get an update on this issue as stable release is coming soon and this bug is marked as RBS for M66.

ellyjones@, Please take a look into it.
Thanks..!
Now that Chrome 67 is out, I think this bug should be closed.

Status: WontFix (was: Assigned)
Agreed.

Sign in to add a comment