http://stackoverflow.com/questions/38029603/chrome-automatically-brings-packaged-app-window-into-foreground-when-selecting-i

@handtrix: Could you please have a look at the attached video and let us know if this is the correct procedure to repro this issue. 

Clicking on "Google Chrome" icon from the Dock opens the Chrome, but Command+Tab remains in Application.

Thank you.

Deleted: 623338.mov 12.2 MB

623338.mov 12.2 MB Download

Thanks a lot you for your response.

I don't think this is the right way to reproduce this issue, since you are trying to reproduce it with 2 chrome apps. I have an issue using a chrome app and a non chrome app.

I have to admit that I was not perfectly clear in my report, so here a more detailed description of what the issue is all about:

To Reproduce:

1. Open Google Chrome
2. Open any chrome app (e.g. World Clock)
3. Open a non Chrome App (e.g. TextEdit)

Now your window stack (z-index) should have the following order:

  Google Chrome
  World Clock
  TextEdit (in the foreground)

4. Now Click the chrome dock Icon

This will result in the following window stack:

  TextEdit
  World Clock
  Google Chrome (in the foreground)

But the window stack I would expect from an app would be the following:

  World Clock
  TextEdit
  Google Chrome

In addition please check out the animated gif I posted under http://i.stack.imgur.com/EqtNV.gif.

Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Over to tapted@ for investigation or routing, since I know they've worked on packaged apps for Mac a bit.

A similar thing was fixed in  Issue 252547 . This is also closely related to Issue 395135. But there's not really much we can do -- it's OSX that decides to raise these windows.

Can you expand on why OS X does that? Is it because both windows belong to the Chrome process?

Yes that's right. There's a process associated with the Dock icon, but that process doesn't create any windows -- they're all owned by Chrome. If you look at the bugs blocked-by  Issue 308382  you'll see some more information about the set of problems that exist. Unfortunately there's not much we can do unless Apple provide OSX with the APIs we use on Windows and Linux to associate groups of windows to a particular "app id" rather than a system process.

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

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

 Issue 308382  is WIP which should fix this. But we should check this with Issue 517682

This is being fixed by RemoteMacViews (Issue 859152). But this will probably never be backported to work with Chrome Apps (too much complexity). It'll apply to PWA windows. Therefore, closing as WontFix.

Looking at Issue 484737 for the PWA equivalent.