New issue
Advanced search Search tips

Issue 822101 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Mar 2018
Cc:
sunn...@chromium.org
vmi...@chromium.org
fdoray@chromium.org
zmo@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Handle window occlusion on Windows

Project Member Reported by sunn...@chromium.org, Mar 15 2018 
Windows can notify us when our application is occluded via RegisterOcclusionStatusWindow/Event. The former will signal a window with a message of our choice. The latter will signal a waitable event.

The previous attempt at this (https://chromium-review.googlesource.com/c/chromium/src/+/920161) used RegisterOcclusionStatusWindow in the browser process but we don't allow D3D/DXGI there AFAIK.

We could instead run this in the GPU process in GLSurface::Initialize (DirectComposition and EGL) and tell it to signal the parent window that's in the browser process.

Comment 1 by fdoray@chromium.org, Mar 15 2018

Mergedinto: 813093
Status: Duplicate (was: Available)
This is actively being worked on. https://crbug.com/813093

According to our tests, the RegisterOcclusionStatusWindow/Event API only notifies us when we exit the states listed at https://msdn.microsoft.com/en-us/library/windows/desktop/hh768892(v=vs.85).aspx.

Do you believe that we could get different results if we were running in the GPU process?

Comment 2 by sunn...@chromium.org, Mar 16 2018 

Thanks for linking to the WIP bug. Great to hear that this is being worked
on. I don't think we would get anything more out of that API. (I thought it
was weird that it's called "occlusion status" but you don't provide any
information about your application's windows to it.)
►

Sign in to add a comment