Use TabStripModelObserver's new API in Browser
Replace old API with new API. This CL is a refactor and has no intended behavior change. The new API callbacks are only invoked when the internal state of TabStripModel is consistent. The old API callbacks would be invoked while the internal state of TabStripModel was inconsistent. FullscreenController's implementation was relying on an inconsistent state for TabStripModel. So FullscreenController is modified too. FullscreenController::IsFullscreenForTabOrPending() checks if |web_contents| is same with the active tab. But when it's handling tab deactivation, the active tab is already changed to the newly activated tab. Therefore we shouldn't assert in that case. Change-Id: I10a9f055ae111d43ba20ad6b9155196abe638e5b Bug: 842194 Reviewed-on: https://chromium-review.googlesource.com/c/1196287Reviewed-by:Scott Violet <sky@chromium.org> Reviewed-by:
Erik Chen <erikchen@chromium.org> Commit-Queue: Sang Woo Ko <sangwoo108@chromium.org> Cr-Commit-Position: refs/heads/master@{#601831}
Showing
This diff is collapsed.
Please register or sign in to comment