Remove old webui History page on desktop and mobile

chrome/browser/android/ntp/new_tab_page_url_handler.cc

Index: chrome/browser/android/ntp/new_tab_page_url_handler.cc
diff --git a/chrome/browser/android/ntp/new_tab_page_url_handler.cc b/chrome/browser/android/ntp/new_tab_page_url_handler.cc
index 18a61b180ee2870a0afb77e99f66e71046f03509..2acf2e7ffc9a3bf87f14a0657704c7f0d49880e2 100644
--- a/chrome/browser/android/ntp/new_tab_page_url_handler.cc
+++ b/chrome/browser/android/ntp/new_tab_page_url_handler.cc
@@ -35,9 +35,7 @@ bool HandleAndroidNativePageURL(GURL* url,
     // TODO(twellington): stop redirecting chrome://history to
     // chrome-native://history when M57 is a distant memory.
     // See http://crbug.com/654071.
-    if (base::FeatureList::IsEnabled(features::kNativeAndroidHistoryManager) &&
-        (url->host() == kChromeUIHistoryHost ||
-         url->host() == kChromeUIHistoryFrameHost)) {

[Ted C, 2017/04/28 18:00:10]

@twellington - I "think" we need to keep kChromeUIHistoryFrameHost here.  I
think if we remove this than any old history users will not get anything (where
we want to send them to native history instead).

57 is not a distant memory by any stretch on Android sadly.

[Theresa, 2017/04/28 18:06:43]

That makes sense. If a user has a chrome://history-frame when they upgrade this
will probably still be hit. Safer to add it back.

[Dan Beam, 2017/04/29 02:39:43]

Done.

+    if (url->host() == kChromeUIHistoryHost) {
       *url = GURL(kChromeUINativeHistoryURL);
       return true;
     }