Delete SoftwareOutputDeviceWinDirectChild.
This software output device implementation created a child window to draw into from the GPU process. This was to prevent some flashes in the blank areas of the window on resize. While investigating https://crbug.com/924975 it seems like drawing directly into the browser HWND no longer causes any issues on Windows 7 or 10. Drawing directly in the browser HWND also fixes the bug where we aren't redrawing exposed regions on Windows 7 with DWM disabled and software compositing. This was caused by the WM_PAINT update region being empty for the browser window because it has the WS_CLIPCHILDREN style. The child window wasn't handling the WM_PAINT message and with DWM disabled Windows doesn't keep it's own copy of the pixels. As a result, nothing was telling the display compositor to paint those pixels again. Bug: 924975, 835906 Change-Id: I70eef78223ea6f18f4898ebb4d973811fa85c1d2 Reviewed-on: https://chromium-review.googlesource.com/c/1450399 Commit-Queue: kylechar <kylechar@chromium.org> Reviewed-by:Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#628433}
Showing
Please register or sign in to comment