GitLab

FullscreenController is tied to the Browser, so when the Browser is
destroyed, any reference to FullscreenController is garbage. Thus,
SadTabCoordinator needs to call [self stop] to break itself down
(and therefore reset its FullscreenDisabler) before the Browser is
completely destroyed in case [self stop] is called by its owning class
after the fact.

Bug: 1154298
Change-Id: Id9ffc055d338972fe360899a14cf596fc7c41a3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572692Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#835718}