New issue
Advanced search Search tips

Issue 869121 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 866760
Owner: ----
Closed: Aug 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Two pages loading in separate windows on separate spaces causes rapid space switching

Project Member Reported by rsesek@chromium.org, Jul 30

Issue description

Chrome Version: 69.0.3497.12
OS: macOS 10.13.6

What steps will reproduce the problem?
(1) Open two Chrome windows and put them on separate macOS spaces
(2) In each window, load (or re-load) a complicated web page (this must be done quickly so that both pages are loading at the same time)
(3) Take hands off keyboard and Chrome will rapidly flip between the two spaces

What is the expected result?
Chrome should not causes macOS spaces switching to occur just because a page is loading.

What happens instead?
Lots of spaces switching when not interacting with the computer. See attached screen recording.



Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 
Cc: ellyjo...@chromium.org
Labels: Proj-MacViews M-70
Status: Available (was: Untriaged)
Ugh, this happens to me too. Someone should probably investigate what causes this. Presumably something is inappropriately calling -[NSWindow makeKey]. 
Mergedinto: 866760
Status: Duplicate (was: Available)
I think I fixed this, but please check canary (>=70.0.3513.0). The merge happened over the weekend, so the m69 beta expected to appear by tomorrow should be fixed too.

(hint: if you expect a MacViews framework issue, be sure to add Proj-MacViews and I'll be more likely to swoop in :).

(trivia: [assuming it is actually a dupe] this is likely a haunt from  Issue 31821  from 2010 and boils down to http://openradar.appspot.com/radar?id=1118405 ).
Seems fixed in canary 70.0.3521.0

Sign in to add a comment