GitLab

Currently the inline rAF loop gets restarted before the page is
notified that the immersive session has ended. This causes some flaky
test cases where the inline callback is serviced before the page knows
that it's okay, since the immersive session has ended. This change
splits the FrameProvider's OnSessionEnded logic such that it can be
notified of the fact that there is no longer an immersive session before
the page is (so that the page is not blocked from requesting a new
immersive session), while only re-starting the inline rAF loops after
the page has been notified.

Fixed: 1062195
Change-Id: I2ccf63d476b7f857bc53e9c15bedc07a13fdfed6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354537Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797812}