RemoteMacViews: Store ui::TextInputClient in views::TextInputHost
There is currently a ui::TextInputClient* stored in BridgedContentView. This is problematic because the ui::TextInputClient lives in the browser process while the BridgedContentView lives in the app process. Cut-and-paste-move textInputClient_ and pendingTextInputClient_ from BridgedContentView to TextInputHost, and make it a member of the BridgedNativeWidgetHostImpl class, using the views_bridge_mac:: BridgedNativeWidgetHostHelper structure to close the gap between the two. This leaves many direct accesses of the ui::TextInputClient from the app process, which we can now replace one-by-one with mojo calls in subsequent patches. Bug: 901490 Change-Id: Ib4497afd4dd7a4e41541eaab170157e1c7eeb90e Reviewed-on: https://chromium-review.googlesource.com/c/1391879 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:Sidney San Martín <sdy@chromium.org> Cr-Commit-Position: refs/heads/master@{#619321}
Showing
This diff is collapsed.
Please register or sign in to comment