background tabs repeatedly coming to foreground without reason |
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9460.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.91 Safari/537.36 Platform: 9460.60.0 (Official Build) stable-channel link Steps to reproduce the problem: 1. Open multiple tabs, and try to read something on one tab (e.g. docs.google.com) 2. After about 10s, suddenly another tab, e.g. memegen becomes the foreground. Click back to original tab, wait 5-15 s, and it happens again. Close memegen, continue reading 3. A new background tab starts grabbing focus What is the expected behavior? Background tabs stay in the background unless they have a notification, or I click them. (neither applies) What went wrong? Background tabs spontaneously and repeatedly jump to the foreground. Did this work before? N/A Chrome version: 59.0.3071.91 Channel: stable OS Version: 9460.60.0 Flash Version: 26.0.0.126 /run/imageloader/PepperFlashPlayer/libpepflashplayer.so This is a new 'borrowed' Grab'n'go Chromebook.
,
Jul 13 2017
Could this be a broken touchscreen issue? Is the tab that pops up always at the same spot on the tab-strip? If you place another tab there (dragging to reorder) does this new tab starts to be the "offender" or is the original one still doing the trick?
,
Jul 13 2017
,
Jul 13 2017
Sadly, I can't check, I've returned the loaner. Your theory sounds very plausible though -- I think it reasonably likely the offending tab was always in the same spot.
,
Jul 13 2017
,
Jul 14 2017
I had a chance to investigate the exact machine from the report. And could not reproduce the issue in a period of ~3h of heavy usage. My suspicion is either dirt or temporary issue with the touch screen causing spurious touches on the tab strip. I will leave it to the UI team to decide on a course of action but I suggest (and the reporter agrees with this proposal) to close the bug as WontFix (can't repro).
,
Jul 14 2017
Recommendation SGTM, closing as WontFix. |
||||
►
Sign in to add a comment |
||||
Comment 1 by jbstjohn@google.com
, Jul 13 2017