Hmm, this would imply background/foreground status is incorrect at launch of the new window. There's another bug that this can be linked to if I can find it, but for now +background scheduler folks who are probably at least interested in an FYI for this.

mlamouri@: Is this something you could take an initial look at?

+gab who is the last person I remember making a lot of changes for the foreground/background machinery. The bugs I was thinking of are  issue 526271  and  issue 560446  -- which is still open and available.

actually +gab for c#3.

Assigning to gab@ as playback will only be blocked for hidden pages. If there is a bug here it's very likely because the page is exposed as note hidden. The fact that opening in a new window is the problem over opening to the current window seems more likely the issue over the background playback logic.

This could be  issue 560446  but I'm not convinced. We inversed the backgrounding logic in M51 (r385608) to make navigations foreground by default (otherwise foreground navigations were backgrounded until navigation commit per having no associated visible state...). So ctrl+click would indeed result in a "foreground" tab until it's focused and unfocused again...

There's been discussion on how to solve this, oysteine@ had a proposal but has since left the team and I haven't had time to loop back around to it.

However,  issue 560446  results in foreground *priority*, widgets are still not considered *visible*. i.e. the same thing happens on session restore (all tabs will have foreground priority until focused/unfocused once), but video playback is stopped nonetheless.

So the problem is that "open in new window" for a bookmark group doesn't have the same behavior as session restore (where this does work despite  issue 560446 ).

+fdoray/chrisha as the restore experts.


PS: What's BackgroundTaskScheduler?! It sounds like a thing the base/task_scheduler folks should be aware of?

BackgroundTaskScheduler is a wrapper around an Android System API for executing tasks when the Chrome executable is not running. On some versions of Android, instead of the system API, Google Play services is used.

This bug has an owner, thus, it's been triaged. Changing status to "assigned".