I've found that some API decisions that we made in LibraryLoader and BrowserStartupController complicate their refactoring / prototyping.
For example both LibraryLoader.get() and BrowserStartupController.get() want you to specify LibraryProcessType, while in reality that argument is used in the context of a couple of methods, the rest of the time specifying LibraryProcessType is just a noise (example: all BrowserStartupController.isStartupSuccessfullyCompleted calls).
This is an umbrella issue for all related changes.
Comment 1 by bugdroid1@chromium.org
, May 15 2018