Tied up BlimpNavigationController to NavigationFeature

blimp/client/core/contents/fake_navigation_feature.cc

Index: blimp/client/core/contents/fake_navigation_feature.cc
diff --git a/blimp/client/core/contents/fake_navigation_feature.cc b/blimp/client/core/contents/fake_navigation_feature.cc
new file mode 100644
index 0000000000000000000000000000000000000000..4903e8fbe1965219103080996d4ee4044fb2d8f1
--- /dev/null
+++ b/blimp/client/core/contents/fake_navigation_feature.cc
@@ -0,0 +1,34 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include <blimp/client/core/contents/fake_navigation_feature.h>
+#include "base/bind.h"
+#include "base/location.h"
+#include "base/memory/ref_counted.h"
+#include "base/threading/thread_task_runner_handle.h"
+#include "url/gurl.h"
+
+namespace blimp {
+namespace client {
+
+FakeNavigationFeature::FakeNavigationFeature() {}
+
+FakeNavigationFeature::~FakeNavigationFeature() {}
+
+void FakeNavigationFeature::NavigateToUrlText(int tab_id,
+                                              const std::string& url_text) {
+  base::ThreadTaskRunnerHandle::Get()->PostTask(

[Kevin M, 2016/08/01 23:41:58]

(See comment in .h)

Why are we posting a task instead of just invoking the method directly?

[shaktisahu, 2016/08/02 17:47:53]

In real world scenarios, the delegates/observers are usually invoked
asynchronously. Posting a task here kind of mimics that.

+      FROM_HERE, base::Bind(&FakeNavigationFeature::NotifyDelegateURLLoaded,
+                            base::Unretained(this), tab_id, url_text));
+}
+
+void FakeNavigationFeature::NotifyDelegateURLLoaded(
+    int tab_id,
+    const std::string& url_text) {
+  NavigationFeatureDelegate* delegate = FindDelegate(tab_id);
+  delegate->OnUrlChanged(tab_id, GURL(url_text));
+}
+
+}  // namespace client
+}  // namespace blimp