customtabs: Allow parallel requests to be processed before native is available.
Parallel requests are initiated when an intent is dispatched to a CustomTabs activity. At that point, native is not guaranteed to be initialized, but the request needs the browser to be initialized, not merely the native library to be loaded. In this case, delay the call until this condition is fullfilled. To that end, add a delayed task mechanism to ChromeBrowserInitializer. Add tests to this class, and while in the neighborhood, convert Runnable to lambdas. Note that this is not exposed to clients yet, as enabling the feature still requires the browser to be initialized. This first CL introduces the mechanism and ensures that existing behavior is preserved. Bug: 901835 Change-Id: I184e1da5ae974458d19f6a88a3f26ba6c443cb57 Reviewed-on: https://chromium-review.googlesource.com/c/1349227Reviewed-by:Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Alexandr Ilin <alexilin@chromium.org> Commit-Queue: Benoit L <lizeb@chromium.org> Cr-Commit-Position: refs/heads/master@{#611054}
Showing
Please register or sign in to comment