Add hooks for capturing meaningful text info, gently.

public/web/WebViewClient.h

Index: public/web/WebViewClient.h
diff --git a/public/web/WebViewClient.h b/public/web/WebViewClient.h
index 366aa4c5fa4ca6eb892d3f792197801b60241ace..f1ffa139f0b19a0dc9e1112fa9748786e324eea7 100644
--- a/public/web/WebViewClient.h
+++ b/public/web/WebViewClient.h
@@ -196,6 +196,10 @@ public:
     // unless the view did not need a layout.
     virtual void didUpdateLayout() { }
 
+    // The frame's document finished layout immediately after the parsing finished.
+    // Another way to put it: first frame after DOMContentLoaded is dispatched.
+    virtual void didFirstLayoutAfterFinishedParsing() { }

[Nate Chapin, 2015/08/21 22:38:31]

This seems like it it is a property of the frame and not the view. Is there a
reason this should be main frame specific? If not, it should probably go on
WebFrameClient.

[dglazkov, 2015/08/21 22:54:53]

It's currently only called on main frame, because it's actually tied to
producing a frame (in the rendering sense -- the WebViewImpl::layout), rather
than just layout (in the document layout sense -- the FrameView::layout). I
don't have a better name for that, but maybe we should invent something.

[Nate Chapin, 2015/08/21 23:00:29]

Ok, makes sense.

I'm mostly concerned about this being OOPIF-friendly. I guess this is currently?
Adding things to WebViewClient just sets off alarms for me.

+
     // Return true to swallow the input event if the embedder will start a disambiguation popup
     virtual bool didTapMultipleTargets(const WebSize& pinchViewportOffset, const WebRect& touchRect, const WebVector<WebRect>& targetRects) { return false; }