Route Touch Selection ContextMenus on Android.
When the touch-selection context menu is re-shown after moving one of the selection handles, it goes through RenderWidgetHostViewAndroid which always sends the request to the mainframe renderer, which is incorrect when the selection is inside an OOPIF. This CL fixes it by having TouchSelectionControllerClientManagerAndroid route the request to the manager's currently active client. If the selection is in an OOPIF, then TouchSelectionControllerClientChildFrame will handle it. We still need to develop tests for touch handle movements & context menus, both for OOPIFs and main frames. Bug: 977215 Change-Id: I3649af49839778fea4462b35b1b11349e00edcc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2382227 Commit-Queue: James MacLean <wjmaclean@chromium.org> Reviewed-by:Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Reviewed-by:
Mohsen Izadi <mohsen@chromium.org> Cr-Commit-Position: refs/heads/master@{#804333}
Showing
Please register or sign in to comment