[Chromecast] Decouple WebContents life cycle from StartParams.
It's possible for a new Intent with the same WebContents, but different values for mutable parameters like enableTouchInput. When this happens, the WebContents would be reinitialized, which breaks an assertion in WebContentsImpl. By storing the WebContents in a separate Controller, we allow it to persist across a reactivation of mStartParamsState where the new WebContents is equal to the previous instance. Bug: internal b/120089917 Test: cast_shell_junit_tests Change-Id: Id9d58b577a887ffff4002ec6fcde578a71752b1f Reviewed-on: https://chromium-review.googlesource.com/c/1352077 Commit-Queue: Simeon Anfinrud <sanfin@chromium.org> Reviewed-by:Luke Halliwell <halliwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#611808}
Showing
Please register or sign in to comment