Unblocking our desired lazy allocation of canvas backing stores via http://trac.webkit.org/changeset/96624/trunk introduced the issue of timing problems when asking if a canvas is accelerated or not. For example, when deciding whether or not to set accelerates drawing on a layer we ask if the canvas is accelerated. If the canvas isn't fully created, we might not know if it's accelerated or not, so we default to returning false. So, we can avoid this issue if we just instead accelerate the layer based off the same logic the canvas would use, namely HTMLCanvasElement::shouldAccelerate().
Created attachment 121778 [details] Patch
Created attachment 121779 [details] Patch
Committed r104616: <http://trac.webkit.org/changeset/104616>