[clean ios] Fix TabCollectionMediator disconnect.

ios/clean/chrome/browser/ui/tab_collection/tab_collection_mediator.mm

Index: ios/clean/chrome/browser/ui/tab_collection/tab_collection_mediator.mm
diff --git a/ios/clean/chrome/browser/ui/tab_collection/tab_collection_mediator.mm b/ios/clean/chrome/browser/ui/tab_collection/tab_collection_mediator.mm
index e6a8eebcbe26236b0c10343400a8aeeda796d7c5..794a4fbabf2a1f438668b8e0439cd89b5bfb58b7 100644
--- a/ios/clean/chrome/browser/ui/tab_collection/tab_collection_mediator.mm
+++ b/ios/clean/chrome/browser/ui/tab_collection/tab_collection_mediator.mm
@@ -49,7 +49,7 @@
 
 - (void)disconnect {
   _webStateList = nullptr;
-  _webStateObserver.reset();
+  _scopedWebStateListObserver->RemoveAll();

[sdefresne, 2017/06/12 09:48:07]

I don't understand the comment that ScopedObserver takes care of clearing
_webStateObserver.

_webStateObserver is std::unique_ptr<web::WebStateObserverBridge> while
_scopedWebStateListObserver is std::unique_ptr<ScopedObserver<WebStateList,
WebStateListObserverBridge>>.

WebStateListObserver != WebStateObserver so they are not related. So you should
remove the comment from the description.

Regarding whether the .reset() call is required or not, I think it should be
present because it unregister the _webStateObserver from WebState at a
known-time instead of doing it when the autoreleasepool is clearer. I think we
should restore the .reset().

[marq (ping after 24h), 2017/06/13 08:18:53]

Yeah, brain fart on my part.

Does it make sense to be using a scoped observer for the WSL observer, but not
for the WebState observer? Shouldn't both be done the same way?

[sdefresne, 2017/06/13 09:00:27]

WebStateObserver is a weird observer that auto-unregister itself in its
destructor (this is one of the rare observer that do it this way).

See web_state_observer.mm:

  WebStateObserver::~WebStateObserver() {
    if (web_state_)
      web_state_->RemoveObserver(this);
  }

It is also one of the only observer that can only observe a single WebState (so
if you want to observe multiple WebStates at the same time you need to use
multiple WebStateObserver, where as with other observers you can observe
multiple instance with the same observer).

 }
 
 #pragma mark - Properties