Improving canvas 2D performance by switching graphics rendering pipeline.

third_party/WebKit/Source/core/html/canvas/CanvasRenderingContext.h

Index: third_party/WebKit/Source/core/html/canvas/CanvasRenderingContext.h
diff --git a/third_party/WebKit/Source/core/html/canvas/CanvasRenderingContext.h b/third_party/WebKit/Source/core/html/canvas/CanvasRenderingContext.h
index 5f210de88467f750e2c4814c2fba594a4400b398..5365700aa77257ac857781f244595f6edf847605 100644
--- a/third_party/WebKit/Source/core/html/canvas/CanvasRenderingContext.h
+++ b/third_party/WebKit/Source/core/html/canvas/CanvasRenderingContext.h
@@ -109,6 +109,7 @@ public:
     virtual void styleDidChange(const ComputedStyle* oldStyle, const ComputedStyle& newStyle) { }
     virtual std::pair<Element*, String> getControlAndIdIfHitRegionExists(const LayoutPoint& location) { NOTREACHED(); return std::make_pair(nullptr, String()); }
     virtual String getIdFromControl(const Element* element) { return String(); }
+    virtual bool shouldAccelerate() const { return true; }

[Justin Novosad, 2016/07/12 19:31:24]

There are already is a method called "shouldAccelerate" on HTMLCAnvasElement,
that makes a decision based on other parameter.  This one should be called
something else to avoid confusion.  Perhaps
isAccelerationOptimalForCanvasContent()

[sebastienlc, 2016/07/13 19:51:02]

Done.

 
     // WebGL-specific interface
     virtual bool is3d() const { return false; }