GitLab

When tab closures are undone, the max/min inset ranges are not set in
the new WKWebView before loading the page, because the session
restoration logic doesn't follow the new tab creation logic.

This change sets the max/min inset ranges whenever the Fullscreen
model is reset, which covers any change of the active WebState.
There will be no-op calls as a result of this since max/min inset
ranges change during rotations, but it shouldn't hurt performance.

Bug: 1149908
Change-Id: Ic94345d4e01854ab7addb70bf27f215b0f3cb590
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552172
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#830982}