Don't use client side buffers with WebGL

Change-Id: I00575f7ebbac89646d65cd6cefbf4715c9bd3914
Reviewed-on: https://skia-review.googlesource.com/c/179249
Reviewed-by: Greg Daniel <egdaniel@google.com>
Commit-Queue: Brian Salomon <bsalomon@google.com>
This commit is contained in:
Brian Salomon 2018-12-19 14:54:12 -05:00 committed by Skia Commit-Bot
parent fdcbe206f5
commit bf3e486a5c

View File

@ -386,7 +386,7 @@ void GrGLCaps::init(const GrContextOptions& contextOptions,
// families rather than basing it on the vendor alone.
// The Chrome command buffer blocks the use of client side buffers (but may emulate VBOs with
// them). Client side buffers are not allowed in core profiles.
if (ctxInfo.driver() != kChromium_GrGLDriver && !fIsCoreProfile &&
if (ctxInfo.driver() != kChromium_GrGLDriver && !fIsCoreProfile && !kIsWebGL &&
(ctxInfo.vendor() == kARM_GrGLVendor || ctxInfo.vendor() == kImagination_GrGLVendor ||
ctxInfo.vendor() == kQualcomm_GrGLVendor)) {
fPreferClientSideDynamicBuffers = true;