Java ContentViewCore class contains too much details on content view related stuff widely open to embedders. In order to stop it from exposing further inner workings and geting more bloated beyond content boundary, I'm thinking of splitting it into an interface and implementation (namely ContentViewCoreInternal or ContentViewCoreImpl), with the former defining tentative APIs consisting of the public methods in use at this moment, and disallow any more changes.
Once its interface is frozen, I can stop worrying about seeing people add more stuff and even out the ongoing breaking-up efforts. This approach is similar to what has been done to native Issue 626764 . The next step is to remove APIs one at a time, and eventually eliminate the entire interface.
Comment 1 by jinsuk...@chromium.org
, Nov 17 2017Status: Assigned (was: Available)