The goal is to eliminate ContentViewCore (the Java class) if possible as well as the native ContentViewCoreImpl class.
Functionality would move into
- ViewAndroid, WindowAndroid
- WebContents or something else on top of that
- other new classes
Some APIs we might also be able to deprecate if there is already another compatible native public content API. (I suspected there are some things for example that could be reached through WebContents[->GetRWH()[->GetView()] from other native entry points, maybe even above content/ such as tab_android.cc.)
This would also move a lot of the event related stuff from the content/ to the ui/layer. For example I'm suggesting that touch events are routed through ViewAndroid into RWHVAndroid (compare to EventTarget which is implemented by aura::Window on desktop).
Comment 1 by siev...@chromium.org
, Mar 30 2016