Fix the logic for always accelerating canvases
Because HTMLCanvasElement::ShouldAccelerate always returned true if the AlwaysAccelerate finch trial was running, it would never hit the path where it creates a ContextProviderWrapper and checks that it is even POSSIBLE to create an accelerated canvas. This CL changes the logic of that function so that features::kAlwaysAccelerateCanvas simply bypasses all of the other heuristics, but still performs the check on the context provider. Bug: 930559 Change-Id: If4d52b6696424488c468fcaa779793dbec9e689b Reviewed-on: https://chromium-review.googlesource.com/c/1478484Reviewed-by:enne <enne@chromium.org> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#633835}
Showing
Please register or sign in to comment