Issue metadata
Sign in to add a comment
|
Detached inspect window will cause chrome and inspect window to not focus and accept mouse or text input
Reported by
bla...@carstickers.com,
Nov 21
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: 1. Go to a page 2. Inspect anything on the page with dev tools in its own detached window 3. Use the inspect window and switch back and forth between the two until the focus bug appears I have been trying to pinpoint the exact action that causes this bug to happen but it seems to happen almost at random. Having two monitors and the dev tools and main chrome window on different screens might be a requirement to get this bug to happen. What is the expected behavior? To be able to click, type, search and use chrome like normal What went wrong? Chrome seems to go into a state where it no longer accepts focus on the first click. Clicking on anything with the exception of the top bar (back, forward, url bar, options/settings) and right click will result is a no action. For instance clicking on a text box in a page will not activate the curser or accept input from typing. Short cuts such as find (ctrl+f/cmd+f) will not open up the search box in the upper right corder. The copy/paste keyboard shortcut will not work and the only way to copy is to right click and click on copy. Basically chrome becomes completely un-usable. The only way to get the inspect window to change tabs or do anything is to click 2 or more times in rapid succession. Closing the detached dev tools will partly restore the focus such as the ability to type in text boxes, however some actions such as the find, copy, paste will continue to not work. Opening back up the inspect widow will quickly put chrome back into the unable to focus state. The only way to completely fix chrome when this happens is to close all windows and force quit. This seems to happen after about 5 to 20 minutes of use with the inspect window. Did this work before? Yes It was working before the update that added the switch to this tab feature Chrome version: 70.0.3538.102 Channel: n/a OS Version: OS X 10.13.6 Flash Version: I have not had this bug happen when the inspect window is attached. I am running mac os 10.13.6.
,
Nov 22
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 70.0.3538.102 using Mac 10.13.6 and Mac 10.14.1 connected with an extended monitor(....Dual monitor) by following below mentioned steps. 1. Launched Chrome 2. Opened a random page and inspected it, to open DevTools 3. Detached the DevTools from the page 4. Moved the detached DevTools to second monitor. 5. Tried shifting the focus between two windows/monitors We were able to focus them when required, without any issues. @Reporter: Could you please check the same in a new profile without any apps & extensions and let us know if the issue still persists. Any further inputs from your end may be helpful.
,
Nov 23
Thanks for the quick response. This has happened with both third party extensions disabled and enabled. I was able to reproduce it when I had three inspect windows open in the background on different tabs. I was using the inspect window, switched back to the page, clicked a few buttons that triggered a api request. When I clicked back on the inspect window it went into the unable to accept focus state. What was interesting is that when I closed the other two inspect windows that were in the background the issue disappeared. I wonder if one of the other inspect windows is stealing the focus or something. I will continue to try to find the exact steps to reproduce it and get back to you.
,
Nov 23
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
,
Nov 26
Tried checking the issue on reported chrome version 70.0.3538.102 using Mac 10.13.6 with the below mentioned steps. 1. Launched Chrome, Connected to an extended monitor. 2. Opened three tabs and inspected all of them. 3. Detached all the three DevTools 4. Switched the focus from one window to other. Everything seemed normal. @Reporter: As we are not very sure about clicking the buttons which triggered api request, it would be helpful if elaborated on it. As per comment#3 adding Needs-Feedback, for the exact test steps which reproduces the issue. Thanks!
,
Dec 4
I was not able to reproduce it. It could be specific to a certain page. Can you visually see which window is focused? Can you please record a screencast with repro? Thank you
,
Dec 4
I have been unable to reproduce this sense updating chrome to 70.0.3538.110. If it happens again I will update the ticket or open a new one with more information on it.
,
Dec 4
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
,
Dec 4
As per comment #7 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Nov 22