[VR] Don't create text input delegates for VR UI
Now that it is impossible to enter the VR Browser, there is no need for android to provide mechanisms for entering text. All child "UI" classes allow for both the KeyboardDelegate and TextInputDelegates to be null, so the browser renderer factory can simply stop creating the classes. This is a speculative fix for the flaky tests described in the bug, and full cleanup of the classes/codepaths that are always null will be done at a future time. Bug: 1114265 Change-Id: I26977ac0faaf504702465369b4a33a2169181b5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2352519 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Auto-Submit: Alexander Cooper <alcooper@chromium.org> Reviewed-by:Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#797547}
Showing
Please register or sign in to comment