ContentViewCore owns and manages GestureStateListeners that performs post-tasks after a certain gesture event has been processed for various classes. My plan is to introduce a new manager for GestureStateListener objects, and let WebContents own it. Embedders are required to get the instance of the manager from WebContents, and add/remove listeners as they want.
A few points to note:
- In WebView, GestureStateListeners can have a references to AwContents. So the manager should be defined in WebContentsInternals to meet WebView gc requirements.
- GestureStateListener is a pure interface without any default implementation. It can be turned to a real 'interface' with default empty method introduced in Java 8.
Comment 1 by jinsuk...@chromium.org
, Nov 28 2017- cvc java will also be one of GestureStateListeners. - Instead of RWHVA -> cvc -> cvc java -> GestureStateListeners, RWHVA -> RenderViewHostDelegateView(WebContentsViewAndroid) -> GestureStateListenerManager(name TBD) -> GSLM java -> GestureStateListeners