+ pbommana@, could you pls try to repro and bisect if possible. Thank you.

Unable to reprodcue the issue using #61.0.3163.39 on Win 10 as per the steps mentioned in comment #0.

Please find the attached screencast and let us know if we missed any steps from our end. That would help us in further triaging of the issue.

Thanks!!

Deleted: 755593.mp4 2.8 MB

	755593.mp4 2.8 MB View Download

Comment 2: Those are all tabs in a single window, which doesn't show the problem.  You need to have overlapping windows with URLs that take a while to load.

Here's more specific repro steps:

1) Visit http://tests.netsekure.org/slow.php?seconds=10 in 4 different windows (one tab per window).
2) Arrange the windows to cascade, with the lowest left window on top:
      *---*
    *---* |
  *---* |-*
*---* |-*
|   |-*
*---*
3) In the lowest window, visit chrome://settings/clearBrowserData and clear *only* "Cached images and files".  This clears the cache so the pages will be slow to load on restart.
4) Visit chrome://restart in the lowest window.

When Chrome restarts, you'll see the status bubble for all the background windows on top of the foreground window.

I can confirm in a clean profile on 61.0.3163.39 (Beta) as well as 62.0.3187.0 (Canary).

Note: This appears to be Windows specific.  I'm not able to repro on Mac or Linux.

cc the Views crew - any ideas?

Confirming steps in comment #3. I can see the same on Canary 62.0.3187.0.

Deleted: repro.png 1.4 MB

	repro.png 1.4 MB View Download

I am starting to doubt if this (behavior observed in comment 3) is really a bug. All I can say is that the "status bar update" over topmost window behavior can be seen in as early as chrome 29.0 (32 bit). My bisect was not successful.

I am able to reproduce the issue based on steps provided in Comment#3, when tried to bisect I saw similar behavior on latest Chrome stable i.e., 60.0.3112.101.

It would be good to know if this is really a regression, since comments 7 and 8 suggest it is not.  It would be easier to track down if it was.

The status bubble is drawn using a separate HWND.  If we set the Z-order of the window incorrectly we could get behavior like what's described here.  I would imagine we want to tell Windows to draw this window just above the parent, as opposed to e.g. "on top".  I'd hope that's not too hard to do, but I'd think that'd be how we're doing it already.

So far I have checked as far as Chrome 53.0.2785.143 and still see the issue, please find attached screenshot for reference. 

I will continue to check further more and update the bug accordingly.

Deleted: 53.0.2785.143.png 63.8 KB

	53.0.2785.143.png 63.8 KB View Download

Removing blocker label, since issue is observed on M53 Builds as well.

Thanks.!

**UI mass Triage** 

We were unable to reproduce this bug . If this bug still reproduces for you, 
please reopen or file a new issue. 

Thanks..!!