Disable Android virtual keyboard when in VR shell

content/browser/renderer_host/render_widget_host_view_android.cc

Index: content/browser/renderer_host/render_widget_host_view_android.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_android.cc b/content/browser/renderer_host/render_widget_host_view_android.cc
index 0253a8caaecd0d511fcee0cb2f697f5506369a1f..8951474a37d5757bd8b8caaf6d427bf72f58008a 100644
--- a/content/browser/renderer_host/render_widget_host_view_android.cc
+++ b/content/browser/renderer_host/render_widget_host_view_android.cc
@@ -443,7 +443,7 @@ RenderWidgetHostViewAndroid::RenderWidgetHostViewAndroid(
       is_showing_(!widget_host->is_hidden()),
       is_window_visible_(true),
       is_window_activity_started_(true),
-      is_showing_overscroll_glow_(true),
+      is_in_vr_(false),
       content_view_core_(nullptr),
       ime_adapter_android_(this),
       cached_background_color_(SK_ColorWHITE),
@@ -776,7 +776,7 @@ void RenderWidgetHostViewAndroid::OnUpdateTextInputStateCalled(
           ? *GetTextInputManager()->GetTextInputState()
           : TextInputState();
 
-  if (!content_view_core_)
+  if (!content_view_core_ || is_in_vr_)

[EhsanK, 2017/01/13 21:55:24]

I was wondering if the intention of the CL was to avoid notifying
ContentViewCore altogether, which I guess does more than just not showing the
VK?

If yes, shouldn't we be updating the renderer process(es) on the page to to stop
sending updates (say in RenderWidget::UpdateTextInputState() we just early
return is |is_in_vr_| is true)? WDYT?

If the goal here is just to stop VK from popping up, then wouldn't modifying the
state so that TextInputState.show_ime_if_needed == false do the trick? This
could also happen in RenderWidget::UpdateTextInputState(). In that case this
method should be not be changed I believe.

[asimjour, 2017/01/16 19:28:41]

This is a temporary solution. For now I want to stop all the popups (keyboard,
text selection, paste popup, ...), after that I should add VR support for all
these popups one by one, and remove the disabling from here.
we can have three different temporary solutions
1- return when it's needed (the current solution)
2- send an IPC to set VR mode in RendererWidget or RendererView.
3- update the consumer of the events so that they don't show anything.
Based on our offline discussion and since this is a temporary solution, I would
rather to stick to the first solution.

[EhsanK, 2017/01/16 20:23:11]

sgtm. The benefit of doing (2) is not sending unused IPC on Android. But since
this situation is temporary, it might not be worth doing because it will be some
code which will be removed soon. Also there seems to be a bit more to sending
the IPC since Selection updates come from RenderFrame and TextInputState from
RenderWidget. Also, you would have to send a "Page" message through
WebContentsImpl and on the renderer side, handle it in RenderViewImpl to notify
all local root RenderFrameImpls and RenderWidgets in that process.

     return;
 
   content_view_core_->UpdateImeAdapter(

[EhsanK, 2017/01/13 21:55:24]

Regarding the second point above: Here I think the UpdateImeAdapter is doing
more than ImeAdapter. The users of this seem to be ImeAdapter,
JoystickScrollProvider, Tab.java for full screen. I am not sure if any of these
are being used in VR mode.

[asimjour, 2017/01/16 19:28:41]

The UpdateImeAdapter is doing more, but other changes are consequence of showing
the keyboard. So, it is safe to stop them all from here.

[EhsanK, 2017/01/16 20:23:11]

Acknowledged.

@@ -953,7 +953,7 @@ void RenderWidgetHostViewAndroid::SelectionChanged(const base::string16& text,
                                                    const gfx::Range& range) {

[EhsanK, 2017/01/13 21:55:23]

Similar to the OnUpdateTextInputStateCalled() above:
The call to base class's SelectionChange will update |selection_text_offset_|,
|selection_range_|, and |selection_text_|. However, AFAIK we never use those
values on Android and in fact, it seems like we should at some point get rid of
the call to the base class code (that is a separate problem of course). Sicne we
do not update the |content_view_core_| at all, then maybe we should not receive
updates to begin with? WDYT?

   RenderWidgetHostViewBase::SelectionChanged(text, offset, range);
 
-  if (!content_view_core_)
+  if (!content_view_core_ || is_in_vr_)
     return;
   if (range.is_empty()) {
     content_view_core_->OnSelectionChanged("");
@@ -1539,7 +1539,7 @@ void RenderWidgetHostViewAndroid::SendBeginFrame(cc::BeginFrameArgs args) {
 
 bool RenderWidgetHostViewAndroid::Animate(base::TimeTicks frame_time) {
   bool needs_animate = false;
-  if (overscroll_controller_ && is_showing_overscroll_glow_) {
+  if (overscroll_controller_ && !is_in_vr_) {
     needs_animate |= overscroll_controller_->Animate(
         frame_time, content_view_core_->GetViewAndroid()->GetLayer());
   }
@@ -1754,8 +1754,8 @@ SkColor RenderWidgetHostViewAndroid::GetCachedBackgroundColor() const {
   return cached_background_color_;
 }
 
-void RenderWidgetHostViewAndroid::SetShowingOverscrollGlow(bool showing_glow) {
-  is_showing_overscroll_glow_ = showing_glow;
+void RenderWidgetHostViewAndroid::SetIsInVR(bool is_in_vr) {
+  is_in_vr_ = is_in_vr;
 }
 
 void RenderWidgetHostViewAndroid::DidOverscroll(
@@ -2079,7 +2079,6 @@ void RenderWidgetHostViewAndroid::CreateOverscrollControllerIfPossible() {
   overscroll_controller_ = base::MakeUnique<OverscrollControllerAndroid>(
       overscroll_refresh_handler, compositor,
       ui::GetScaleFactorForNativeView(GetNativeView()));
-  is_showing_overscroll_glow_ = true;
 }
 
 }  // namespace content