WebViewChromiumFactoryProvider provides a bunch of functionality for posting tasks to the UI thread, and a bunch of glue classes use this functionality. This creates several circular dependencies where the WebViewChromiumFactoryProvider creates a class which depends on WebViewChromiumFactoryProvider to post tasks to the UI thread.
We should move all the UI-thread task logic into WebViewChromiumRunQueue instead to avoid these circular dependencies.
This is especially relevant now that we're adding a support library glue since we want to share some functionality between the support library glue and the existing webkit glue - and circular dependencies in the webkit glue make it harder to break out classes with shared functionality.
Comment 1 by bugdroid1@chromium.org
, Feb 16 2018