Reland: Allow OffscreenCanvas to access the high-performance GPU.
(Relanding with new tests skipped on Mac NVIDIA Retina, which forces the integrated GPU due to graphics driver bugs.) Instead of only checking whether the containing frame is same-origin with respect to the top-level document during transferControlToOffscreen, check in the OffscreenCanvas constructor, both for the main thread as well as dedicated workers. Dedicated workers are same-origin per specification, so always grant access to the discrete GPU in this scenario. Add new pixel tests that verify WebGL-rendered OffscreenCanvas into an ImageBitmapRenderingContext (i.e., where the OffscreenCanvas was not originally tied to a canvas element). On dual-GPU macOS devices, also verify the active state of the low-power and high-performance GPUs. Simplify some of the tests most recently written for low/high-power GPU switching. Bug: 1048892 Change-Id: I20b7150029fa83d7fe066b8347bf150a0ed45d21 Tbr: kainino@chromium.org Tbr: fserb@chromium.org Tbr: jdarpinian@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068645Reviewed-by:Kenneth Russell <kbr@chromium.org> Reviewed-by:
James Darpinian <jdarpinian@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#743686}
Showing
Please register or sign in to comment