[TTS] Add an ACK message to SelectWordAroundCaret.

content/renderer/render_view_impl.cc

Index: content/renderer/render_view_impl.cc
diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc
index e3ea8995b0e467c49506715807d8219ed1248013..5822f6d8e570b983795dfc39b5c82f4e5b8c52cb 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -1294,7 +1294,22 @@ void RenderViewImpl::OnSelectWordAroundCaret() {
     return;
 
   input_handler_->set_handling_input_event(true);
+#if defined(OS_ANDROID)

[aelias_OOO_until_Jul13, 2017/02/22 03:36:01]

I'd prefer it not be OS_ANDROID.  This makes compile errors hard to catch and
unit tests hard to write.

[Donn Denman, 2017/02/22 23:13:01]

Done.

+  int start_adjust = 0;
+  int end_adjust = 0;
+  blink::WebRange initial_range = webview()->focusedFrame()->selectionRange();
+  bool did_select = webview()->focusedFrame()->selectWordAroundCaret();

[aelias_OOO_until_Jul13, 2017/02/22 03:36:00]

I'm missing a bit of context; why do we set a caret in the first place?  Is this
only for editable boxes?

[Donn Denman, 2017/02/22 23:13:02]

Sorry about the lack of context.  When the user taps on plain text Blink creates
a caret selection.  When CS decides to show the UX we call selectWordAroundCaret
to select the word.

+  if (did_select) {
+    blink::WebRange adjusted_range =
+        webview()->focusedFrame()->selectionRange();
+    start_adjust = adjusted_range.startOffset() - initial_range.startOffset();
+    end_adjust = adjusted_range.endOffset() - initial_range.endOffset();
+  }
+  Send(new ViewHostMsg_SelectWordAroundCaret_ACK(GetRoutingID(), did_select,
+                                                 start_adjust, end_adjust));
+#else
   webview()->focusedFrame()->selectWordAroundCaret();
+#endif
   input_handler_->set_handling_input_event(false);
 }