Check that we have a focus manager in aura before trying to set focus.

chrome/browser/ui/views/tab_contents/native_tab_contents_container_aura.cc

Index: chrome/browser/ui/views/tab_contents/native_tab_contents_container_aura.cc
diff --git a/chrome/browser/ui/views/tab_contents/native_tab_contents_container_aura.cc b/chrome/browser/ui/views/tab_contents/native_tab_contents_container_aura.cc
index 97c126553ed4f68f2bee38ebdd0a8f89cc1a479d..7306e5909896c1ef46574c580f0fcfc50525d04f 100644
--- a/chrome/browser/ui/views/tab_contents/native_tab_contents_container_aura.cc
+++ b/chrome/browser/ui/views/tab_contents/native_tab_contents_container_aura.cc
@@ -113,7 +113,7 @@ void NativeTabContentsContainerAura::RequestFocus() {
   // that should also have focus, RequestFocus() is invoked one the
   // TabContentsContainer.  In order to make sure OnFocus() is invoked we need
   // to clear the focus before hands.
-  {
+  if (GetFocusManager()) {

[sky, 2011/11/28 23:36:08]

This seems fine, but I wonder why we don't have it on the windows side. I would
expect that if we're invoking RequestFocus when this container isn't in a widget
we would do the same on windows. Are we really invoking RequestFocus when not in
a widget?

     // Disable notifications.  Clear focus will assign the focus to the main
     // browser window.  Because this change of focus was not user requested,
     // don't send it to listeners.