I'm having this same issue. Only for me it's the reverse of what's pictured in the video: Chrome stays on top of everything else. Clicking a Finder window, for example, does not bring the Finder window over top of Chrome. I chatted with Apple support at least 3 different times, and they said the issue definitely lies with Chrome. I've reported it here: https://productforums.google.com/forum/#!topic/chrome/snRs7ZBChwg;context-place=forum/chrome

And other's have reported it here: https://discussions.apple.com/message/31044886#31044886

At least 2 of the Apple support agents were able to reproduce it right then and there on their own Macs. Definitely a problem that needs attention.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

mac triage: tnijssen@, can you take a peek at this? in particular does it happen with MacViews?

I opened a Finder window and pulled Chrome over top of it. Using Mission Control to select the Finder window brought it to the foreground as expected. I'm on Chrome version 69.0.3486.0.

Also, MacViews was enabled when I tried that.

Tried it without MacViews and the behavior was still as expected.

For me it's inconsistent. 80% of the time it does not work correctly. Just after a reboot (or something? no idea) it'll work correctly for a short but glorious time. 

I used 3 finger swip up to switch between windows and apps all the time. So it's very frustrating when trying to go from Chrome to something else and Chrome stays on top.

I have no idea if this is a factor (but Chrome has another bug that's triggered by this), but I switch between my MacBook Pro's screen and an external display frequently. 

Here's a screencap of me demonstrating this bug: https://drive.google.com/file/d/1mHZ3xmcAAUeba61yXW52Kd73fK9V_mfB/view?usp=sharing

I'm using 3-finger swipe-up to get to Mission Control, then clicking on the Finder window that's behind the Chrome window. Chrome stays on top.

Though you'll notice in one instance Finder actually moves to the top. As I was recording this, I figured out that (for some reason, I have no idea why), if I click on the top-bar of the finder window, when selecting it, it will then move to the front over chrome, as it should. However, this is not expected behavior as macOS provides a highlight "frame" around the whole thing, indicating that clicking anywhere in the window should bring it to the foreground.

I'm on Chrome 67.0.3396.99 and macOS 10.13.5 (17F77). Though it's been happening for some time on many previous versions of Chrome and macOS.

That anomaly where clicking the topbar fixed it, hasn't persisted. It no longer works. But the overall issue persists.

I still can't recreate this bug with Chrome 67.0.3396.99. Could you share your Mission Control settings so I can see if they might differ from mine?

https://drive.google.com/file/d/1l4gE4pwA8hMD6QNyKp9vGKcy9U-FUKp4/view?usp=sharing

I brought it up with Apple support and they were able to recreate it on a few of their machines, but at least one it didn't occur on. So I'm not sure if there's a set of circumstances that causes it to kick in, or what. But I'm not the only one, as the google and apple support threads I linked to previously, show.

I set my MacBook's Mission Control settings to be the same as the ones you posted and still can't reproduce the bug.

Could you try the following steps for me and report back if the bug is still occuring:
1) Navigate to chrome://flags
2) Search for the flag views-browser-windows
3) Enable the flag titled "Use Views browser windows instead of Cocoa."
4) Relaunch Chrome
5) Try to reproduce the bug

Thank you.

I tried it. No change. It seems Illustrator (maybe other Adobe products) have the same issue. I'm not sure if that's helpful. But found it interesting. I suppose it could mean the issue lies elsewhere. Though the OP seemed like he was seeing something wrong in Chrome. Apple also claimed it was an issue in Chrome (and other 3rd party software not properly implementing priority). 

mac triage: over to avi@ :)

Does this mean someone else will be looking into it?

**UI mass Triage**

We were unable to find repro steps for this bug. If you have more data to
reproduce this bug or have clear repro steps, please reopen or file a new issue.
Thanks!