Don't focus the location bar for NTP navigations in non-selected tabs.

chrome/browser/ui/browser.cc

Index: chrome/browser/ui/browser.cc
diff --git a/chrome/browser/ui/browser.cc b/chrome/browser/ui/browser.cc
index b64ad9188e41876adfbc062c9ba58453894c622b..c994e3d76974f4125dc936bc9518135b8941a024 100644
--- a/chrome/browser/ui/browser.cc
+++ b/chrome/browser/ui/browser.cc
@@ -1551,6 +1551,10 @@ void Browser::BeforeUnloadFired(WebContents* web_contents,
 }
 
 bool Browser::ShouldFocusLocationBarByDefault(WebContents* source) {
+  // Focus if we're going to the NTP, but only if it's in the active tab.

[Peter Kasting, 2017/01/12 18:24:04]

Nit: This might be clearer as "Navigations in background tabs shouldn't change
the focus state of the omnibox, since it's associated with the foreground tab."

[Charlie Reis, 2017/01/12 19:26:54]

Done.

+  if (source != tab_strip_model_->GetActiveWebContents())
+    return false;

[Peter Kasting, 2017/01/12 18:24:04]

Does this mean that, when a user switches to a now-navigated-to-the-NTP
background tab, the location bar won't be focused, but it should be?  Of course
that wouldn't have worked before either, I'm just wondering if there's a
secondary bug here that a background NTP navigation should mark the saved state
for that omnibox as "focused".

[Charlie Reis, 2017/01/12 19:26:54]

Yes, you're right that there's a secondary bug, and it affects Stable and Canary
today.  I've filed https://crbug.com/680624 for it.

+
   const content::NavigationEntry* entry =
       source->GetController().GetActiveEntry();
   if (entry) {