Route selection bounds updates through WebLayerTreeView

public/platform/WebLayerTreeView.h

Index: public/platform/WebLayerTreeView.h
diff --git a/public/platform/WebLayerTreeView.h b/public/platform/WebLayerTreeView.h
index 43549b492355b9c7beb61ff3df1b4bbd4d9d7fa7..c8c0157ff383f7f86fd54b24cb2ccab5f35b2e79 100644
--- a/public/platform/WebLayerTreeView.h
+++ b/public/platform/WebLayerTreeView.h
@@ -42,6 +42,7 @@ class WebLayer;
 struct WebPoint;
 struct WebRect;
 struct WebRenderingStats;
+struct WebSelection;
 
 class WebLayerTreeView {
 public:
@@ -125,6 +126,10 @@ public:
         const WebLayer* outerViewportScrollLayer) { }
     virtual void clearViewportLayers() { }
 
+    // Used to update the active selection region.
+    virtual void registerSelection(const WebSelection& selection) { }
+    virtual void clearSelection() { }

[abarth-chromium, 2014/06/13 21:38:15]

Why does the WebLayerTreeView need to be aware of the selection?  I would have
just expected the selection handles to be embedded in the layer tree somewhere.

[jdduke (slow), 2014/06/20 17:15:59]

I considered attaching the handles to a given layer, but that adds state to
every layer for tracking such (sparse) information, when really the handles are
a singleton (one set per tree), so this seemed the simplest approach.

+
     // Debugging / dangerous ---------------------------------------------
 
     // Toggles the FPS counter in the HUD layer