Improvement of canvas webgl: Check the gpu acceleration before using CanvasResourceProvider |
|||
Issue descriptionCurrently, when HTMLCanvasElement creates image buffer (soon will be changed to CanvasResourceProvider as in https://chromium-review.googlesource.com/c/chromium/src/+/864630) for webgl rendering context, it simply uses GPU Acceleration mode without checking whether the Gpu compositing is actually enabled at all. On the other hand, the implementation for canvas with 2d rendering context did a good job in having a ShouldAccelerated method. We should do the same for webgl too.
,
May 11 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/91777df515fb03be25dbd7c9faf1c86bb7460985 commit 91777df515fb03be25dbd7c9faf1c86bb7460985 Author: xlai <xlai@chromium.org> Date: Fri May 11 15:59:07 2018 Remove TODO comment and add DCHECK to CanvasResourceProvider A follow-up CL of https://chromium-review.googlesource.com/1050618. TBR=junov@chromium.org Bug: 802053 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I221087839763bdf3e09f642a659b7ed322f20492 Reviewed-on: https://chromium-review.googlesource.com/1055480 Reviewed-by: Olivia Lai <xlai@chromium.org> Commit-Queue: Olivia Lai <xlai@chromium.org> Cr-Commit-Position: refs/heads/master@{#557894} [modify] https://crrev.com/91777df515fb03be25dbd7c9faf1c86bb7460985/third_party/blink/renderer/platform/graphics/canvas_resource_provider.cc
,
May 11 2018
,
Oct 31
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, May 10 2018