# TotalFinder Window remains above when opening new Google Chrome incognito window from dock

**URL:** <https://discuss.binaryage.com/t/totalfinder-window-remains-above-when-opening-new-google-chrome-incognito-window-from-dock/668>\
**Category:** TotalFinder\
**Created:** [October 27, 2013, 11:57pm UTC](https://discuss.binaryage.com/t/totalfinder-window-remains-above-when-opening-new-google-chrome-incognito-window-from-dock/668 "2013-10-27T23:57:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZhimingWang](https://discuss.binaryage.com/user_avatar/discuss.binaryage.com/zhimingwang/32/1552_2.png) [@ZhimingWang](https://discuss.binaryage.com/u/ZhimingWang)\
**Post date:** [October 27, 2013, 11:57pm UTC](https://discuss.binaryage.com/t/totalfinder-window-remains-above-when-opening-new-google-chrome-incognito-window-from-dock/668/1 "2013-10-27T23:57:17Z")

</div>

So I have a problem as described in the title. Below are the details.

OS version: OS X 10.8 or 10.9 (same issue on both versions)  
TotalFinder version: TotalFinder 1.5.2 (maybe also on earlier builds; I can’t recall exactly)

Steps to reproduce the problem:

1. Open a Google Chrome window, and leave it there.
2. **Quickly** switch to a Finder window (you know, I mean with TotalFinder).
3. **Quickly** open a Google Chrome **Incognito** window from dock: `Dock--Google Chrome--New Incognito Window`.

Expected behavior:  
Control switches to Google Chrome, and new Chrome window on top of screen.

Actual behavior:  
Control switches to Google Chrome (menu bar), but **Finder window still stays on top of the new Chrome window**.

Here are the screenshots:

**Before:**

 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/712528f1275e5a6911d93c674f26a95d53757ca94b.png)

**After:**

 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/70809525cc0651a947e3790845f7ba3a0d5ff27432.png)

Note that the steps described above is not the only way to produce the problem; but I found it to work every time I tried.

Also, I have done the same tests on the original Finder ( **without TotalFinder** ) and did **not** see the wrong behavior. So I guess this is an issue on TotalFinder’s part (or Chrome, but chances are smaller).

At last, although I didn’t see any correlation with the issue, I will post my TotalFinder configs:

 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/726d597e7260cc394ff4ba382968d298dd878a0a49.png)  
 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/731c017f30890a1583263d96a10717e456ba07e611.png)  
 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/7411522e731ea5319693bc78b1e116ea6287a2e350.png)  
 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/75166d5c471c3ae42dbbea418ac286f5c12ce7d17a.png)  
 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/761326cf19a917666a07201fcce8aeb6c5cd2dc52a.png)  
 ![](https://discuss-s3.binaryage.com.s3.amazonaws.com/773c0a4c9b5c604b2a1c92af937cbc1ac32c122dbf.png)