Thanks for your report.

I can't reproduce this with 66.0.3359.117 on 10.13.5 Beta 17F45c.

When you say the problem doesn't occur on a clean install from a different startup disk, do you mean the exact same versions of 10.13 and of Chrome 66.0.3359.117?

Can you attach a screen recording of the behavior? QuickTime can make these.

Thanks for the comment.
Yes, exact same versions of macOS and Chrome, but when I say clean I mean that I've tweaked the system I normally work with, e.g. no SIP, Gatekeeper turned off.
Didn't realize you could record the behavior with QT. I'll try this out and post again.

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

I've got a screen recording but it's gigantic – any suggestions as to how to reduce it in size? I could shorten it, not show so many instances of the behavior, or save it in a different format perhaps?

Unable to reproduce the issue in reported chrome version 66.0.3359.117 using Mac 10.13.1 with the below mentioned steps.
1. Launched chrome
2. Maximised the window
3. Resized it to normal(...from maximised mode)
4. Clicked on other applications.
We observed that the focus has been shifted on to the current clicked application. Attaching the screencast for reference.

@Reporter: Could you please have a look at the screen cast and let us know if we have missed anything in the process. Any further inputs from your end may be helpful.

Deleted: 835266.mp4 1.6 MB

	835266.mp4 1.6 MB View Download

Thanks for the continued interest. Had a look at the recording (I'd be interested to know how you can produce such a small file size, btw), but this doesn't surprise me. As I already mentioned, the behavior only seems to occur when using my particular profile. Don't want to have to set up everything again, so what do you need to know about my system? Extensions? – same thing happens when they're all removed. Don't know if it could affect the browser, but did you also disable SIP (I'll now try enabling it again)? I can list every little tweak if necessary. I'm new to this (reporting bugs) so I'd be grateful for any suggestions as to what info I could supply?

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

Unable to reproduce the issue in reported chrome version 66.0.3359.117 and latest chrome 68.0.3405.0 using Mac 10.13.1 with the below mentioned steps.
1. Launched chrome reported version and Maximised the window
3. Resized it to normal and clicked on other applications, observed focus has been shifted on to the clicked application.

@Reporter: Try to test this issue by creating new person with no apps and extensions in it and let us know if the issue still persists.

Thanks!

As already indicated (see initial report), the issue does not occur when using a different profile.

Needless to say, re-enabling System Integrity Protection made no difference. Neither did undoing a few other minor system tweaks.

Rather than just disabling my current extensions, I'll now remove them from Chrome and test again.

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

La même chose. 
No extensions whatsoever, issue still persists with my profile.

Unable to reproduce the issue on mac 10.13.3 using chrome reported version #66.0.3359.117.

Observed that window did not stay active and did not stay in front of all other windows (regardless of which app) after exiting Full Screen mode, Toolbar items are also clickable as expected.

As the issue is not reproducible from TE-end. Hence, requesting someone from UI>Browser>FullScreen team to please have a look into the issue and adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

+sdy@ for any potential fullscreen insight.

Super interesting. OK, I have a few questions:

- Do you have multiple displays?

- When you say that you tried with a separate profile, do you mean a separate profile within Chrome? If so, does that mean that you can have Chrome windows from both profiles open at the same time and trigger the bug with one and not the other? If not, could you try that?

- Do you have any software running that does window management? I think I recognize Adobe CC and Time Machine in your menu bar, but not the two in between.

Re. your other question, my tool of choice for video crunching is ffmpeg (installed via Homebrew):

    ffmpeg -i screen.mov -profile:v main -level 3.1 -preset medium screen.mp4

The options in the middle make it playable on more devices (e.g. iPhones), and you can add "-crf 25" to adjust the quality (bigger numbers are lower quality, usually 20-30 is a good range to play with if you have to) right before the output filename.

Oh, one more question:

- Do you have/use any Chrome apps (chrome://apps) other than the defaults?

Thanks very much for not giving up on this, I was just about to downgrade once more.
First let me answer your questions:

- No, I don't have multiple displays (but I could hook another one up to see if it makes a difference).

- By separate profile I meant different user, i.e., logging in to macOS as someone else. If I add a person under Manage People, the bug will still persist and occur for both profiles. 

- As far as I can tell I don't have third party software running window management. The two apps you noticed in the menu bar were antivirus and adblocking software, but the bug can still be triggered when these are removed from the Login Items.

- Your last question proved interesting. I have Google Drive installed but I don't think I've ever used it. However, I also have Google Chrome Canary, and lo and behold, entering and exiting Full Screen mode in Canary (signed in or not) does NOT effect window behavior! It will also behave normally when running parallel to the buggy Chrome.

So I ask myself, what's different about Canary's window management?

Finally, for what it's worth, I'm attaching another recording of the bug showing how entering Split View can (sometimes!) temporarily fix the issue, rather than having to close the problematic window. Oh, and thank you sdy for suggesting I use ffmpeg – worked like a charm.

Deleted: bug.mp4 8.4 MB

	bug.mp4 8.4 MB View Download

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

Thanks, that actually helps a lot. There are two possible differences between stable and canary that I want to investigate:

- There's a bug in stable that has been fixed in canary (and the fix will make it to stable soon).
- Your user data directory contains some setting that causes this behavior.

Something I'd like you to try: run Chrome from a Terminal, but pass `--user-data-dir=…`, like this:

    /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir="$HOME/Desktop/temporary_udd"

"temporary_udd" will be created on your Desktop and be essentially a fresh copy of Chrome. See if you can reproduce the bug. If that fixes it, great. Visit chrome://version in your normal/broken instance of Chrome and copy and paste the contents here, and maybe we can sort out the trigger.

If you're feeling extra adventurous, you can also make a copy of your real user data dir (~/Library/Application Support/Google/Chrome) and pass the copy's path to canary:

    /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --user-data-dir="$HOME/Desktop/udd_copy"

…and then see if you can trigger the issue. You don't want to point canary at your real UDD because it might no longer work with the current stable release.

Unfortunately, this does reproduce the bug. 

Would it still do any good to post the contents of chrome://version in my broken instance of Chrome?

If I pass a copy of my user data dir to Canary and it then breaks, is there a way of undoing this?

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

> Unfortunately, this does reproduce the bug.

"This", meaning running with --user-data-dir=… gives you a fresh "instance" of Chrome (including first-run prompts) that still reproduces the bug? If so, that's unexpected because all of Chrome's state should be contained in that directory.

> Would it still do any good to post the contents of chrome://version in my broken instance of Chrome?

Actually, yes — there's info about your field trial configuration that could be helpful.

> If I pass a copy of my user data dir to Canary and it then breaks, is there a way of undoing this?

It shouldn't. That command line flag only applies to that particular run; you can even run multiple instances of Chrome by passing them different --user-data-dir flags.

- - -

If passing --user-data-dir does not fix it but running in a separate macOS user does, then I'd suspect something in your macOS user account. The fact that canary works is also encouraging. It could mean that the underlying bug is fixed in canary and will make its way to stable soon.

Sorry, I don't think I understood the instructions at first. I was feeling adventurous and did the same thing with Canary.

So ...
Ran Chrome from Terminal, using a temporary UDD – bug is reproducible; ran Canary in the same way – bug is not reproducible.

chrome://version in my normal/broken instance of Chrome:

Google Inc.
Copyright 2018 Google Inc. All rights reserved.
Google Chrome	66.0.3359.139 (Official Build) (64-bit)
Revision	a020eddf0d85fe84d4a6787b304f50aafb670969-refs/branch-heads/3359@{#767}
OS	Mac OS X
JavaScript	V8 6.6.346.26
Flash	29.0.0.140 /Library/Internet Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin
User Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36
Command Line	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end
Executable Path	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path	/Users/mickser/Library/Application Support/Google/Chrome/Default
Variations	c134752e-b8b72c88
5f419cc9-ca7d8d80
a6674cf-ca7d8d80
3095aa95-3f4a17df
d52c4ff7-d52c4ff7
47e5d3db-3d47f4f4
4dc30737-b8a5ea08
f9884634-659882c0
121ae2bc-ca7d8d80
57f575bb-f23d1dea
ceff87ec-ca7d8d80
44827ee5-ca7d8d80
9b54a08f-28ad44a
120703dd-3f4a17df
d0ecf1da-ca7d8d80
4b61504a-c9eb6633
ef05a96e-e2c3ac67
9773d3bd-f23d1dea
8e3b2dc5-93702590
9e5c75f1-1039a221
c322f799-2dbe5f9
3de1fbf2-3d47f4f4
f79cb77b-3d47f4f4
4ea303a6-ecbb250e
2b33233e-d8253d6f
72606c4f-3f4a17df
58a025e3-c2b41702
2a32876a-ca7d8d80
4bc337ce-69465896
9a2f4e5b-d226bfeb
494d8760-52325d43
f47ae82a-86f22ee5
3ac60855-486e2a9c
f296190c-b7d97d3d
4442aae2-a5822863
ed1d377-e1cc0f14
12e17bc5-e1cc0f14
75f0f0a0-e1cc0f14
e2b18481-6e3b1976
e7e71889-4ad60575
b1ceb06f-3ac589b9
94e68624-803f8fc4

> If passing --user-data-dir does not fix it but running in a separate macOS user does, then I'd suspect something in your macOS user account.

I half expected this might be the case. I've migrated my content twice in the last six years, so something probably got mixed up along the way.
Before I downgrade again, I'll seriously consider starting afresh with a clean macOS install, then add my apps, data, and customization bit by bit. But I'll look forward to an even more stable 'stable' Chrome in the future.

If I don't hear anymore from you, thanks again for your efforts.

> I'll look forward to an even more stable 'stable' Chrome in the future.

One more option: you can try Chrome beta. It may or may not have the fix right now, but will get it several weeks earlier than stable. The main thing to keep in mind is that Beta uses your normal Chrome UDD, and it may change it in ways that are incompatible with the current stable.

> If I don't hear anymore from you, thanks again for your efforts.

No problem. I'm marking this as WontFix, but I'll stay cc'd on the bug in case you have new info to share in the future. Thanks again for filing it.

Dispelled!
Not sure, but I think it was the update to Mojave (this week) rather than the latest version of Chrome (Version 69.0.3497.100) that fixed it. Don't feel like downgrading to an earlier version of Chrome just to be sure ;-)