Issue metadata
Sign in to add a comment
|
Can't Alt-tab away from Chrome. Seems to hog the foreground
Reported by
peter.n...@gmail.com,
Feb 21 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Stand up Debian 9 VM in Google Cloud 'Compute Engine' 2. Install Mate Desktop, NoMachine, Chrome/Chromium 3. Connect remotely with NoMachine 4. Open Chrome and a few other Windows 5. Try Alt-tab behavior I can give highly detailed steps if you want... Or even give remote access to the server in question I suppose... What is the expected behavior? That Alt-tab AND clicking in the task bar would allow other windows to become foregrounded. What went wrong? Alt-tab AND clicking in the task bar is ineffective at bringing other windows in front of Chrome/Chromium. Everything else works fine. I can Alt-tab away from all other apps tried. Both Chrome AND Chromium however, seem to hog the foreground. The Alt-tab animations work, but upon releasing the Alt key - The desired other app window does not come forward. Interestingly, minimizing and restoring a Chrome window temporarily allows other windows to be foregrounded by clicking in the task bar (but doesn't help with Alt-tab) Did this work before? Yes Can't recall. Chrome version: 64.0.3282.167 Channel: stable OS Version: Debian 9 (stretch) Flash Version: There is a long-closed bug here getting a pretty constant trickle of similar reports going back to 2011, and as recent as Feb/14/2018: https://bugs.chromium.org/p/chromium/issues/detail?id=81076 Claimed to be dup of 74604, but seems only a passing similarity to me...
,
Feb 22 2018
Thanks for filing the issue! This issue seems to be out of scope for triaging from ET team, as it speaks about setting up a Debian 9 VM in Google Cloud "compute engine", installing mate desktop and remotely connecting to NoMachine. Requesting someone from TE-Hyd team to have a look into this and help in further triaging, hence adding label TE-NeedsTriageFromHYD.
,
Feb 22 2018
I thought you might say that... It's strange that every other tools works though, just not Chrome, or Chromium, or Opera for that matter. Firefox works fine, so I guess I will have to give that a try for a while!
,
Feb 22 2018
Just one more thing - It's pretty clear that Chrome/Chromium is rendering its window in some way that is different to most other Linux programs. It it possible there could be some rendering setting in Chrome Flags that _might_ restore the functionality that is problematic in my situation? Just asking...
,
Feb 23 2018
Unable to triage this issue from TE-End because of non availability of cloud platform test setup, hence adding TE-NeedsTriageFromMTV label for further triage from MTV
,
Feb 26 2018
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, Feb 21 2018