Fix canvas rate limiting for certain canvas scenarios.

In certain situations the "SetIsBeingDisplayed" notification for
CanvasRenderingContext2D - coming from HTMLCanvasElement - occurs
before the Canvas2DLayerBridge is allocated. In order to reliably
allocate the rate limiter when needed, set the display status of the
Canvas2DLayerBridge upon its allocation / installation.

Bug: 1038670
Tbr: fserb@chromium.org
Change-Id: I8029462ec7c94f4644763cd8b662471b69a7d64b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999085
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Juanmi Huertas <juanmihd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732282}

third_party/blink/renderer/core/html/canvas/html_canvas_element.cc

@@ -1106,11 +1106,15 @@ void HTMLCanvasElement::SetCanvas2DLayerBridgeInternal(
       canvas2d_bridge_ = CreateUnaccelerated2dBuffer();
   }
 
-  if (canvas2d_bridge_)
-    canvas2d_bridge_->SetCanvasResourceHost(this);
-  else
+  if (!canvas2d_bridge_)
     return;
 
+  canvas2d_bridge_->SetCanvasResourceHost(this);
+  bool is_being_displayed =
+      GetLayoutObject() && GetComputedStyle() &&
+      GetComputedStyle()->Visibility() == EVisibility::kVisible;
+  canvas2d_bridge_->SetIsBeingDisplayed(is_being_displayed);
+
   did_fail_to_create_resource_provider_ = false;
   UpdateMemoryUsage();
 

third_party/blink/renderer/modules/canvas/canvas2d/canvas_rendering_context_2d.cc

@@ -674,7 +674,7 @@ scoped_refptr<StaticBitmapImage> blink::CanvasRenderingContext2D::GetImage(
 
 void CanvasRenderingContext2D::FinalizeFrame() {
   TRACE_EVENT0("blink", "CanvasRenderingContext2D::FinalizeFrame");
-  if (canvas() && canvas()->GetCanvas2DLayerBridge())
+  if (IsPaintable())
     canvas()->GetCanvas2DLayerBridge()->FinalizeFrame();
   usage_counters_.num_frames_since_reset++;
 }