Fire accessibility focus/blur events on root web document.

content/browser/accessibility/browser_accessibility_manager_win.cc

Index: content/browser/accessibility/browser_accessibility_manager_win.cc
diff --git a/content/browser/accessibility/browser_accessibility_manager_win.cc b/content/browser/accessibility/browser_accessibility_manager_win.cc
index 98350450151f27bb4ad6781dea6f829cd2476ecc..dee3b05a79a1d213f13f4e3df075d635b032630e 100644
--- a/content/browser/accessibility/browser_accessibility_manager_win.cc
+++ b/content/browser/accessibility/browser_accessibility_manager_win.cc
@@ -97,6 +97,18 @@ void BrowserAccessibilityManagerWin::RemoveNode(BrowserAccessibility* node) {
   }
 }
 
+void BrowserAccessibilityManagerWin::OnWindowFocused() {
+  if (focus_ != root_)
+    NotifyAccessibilityEvent(ui::AX_EVENT_FOCUS, root_);
+  BrowserAccessibilityManager::OnWindowFocused();

[David Tseng, 2014/04/02 22:05:05]

Does ordering matter here? If I were a client, I may expect to see the root
focused first, then the descendant node focused.

[dmazzoni, 2014/04/02 22:09:55]

Yes, that's the order you'll get: first root, then the descendant (fired by the
parent class).

+}
+
+void BrowserAccessibilityManagerWin::OnWindowBlurred() {
+  if (focus_ != root_)

[David Tseng, 2014/04/02 22:19:51]

Sorry; this was the one I meant to comment on; seems we should blur the focused
node first then the root right?

+    NotifyAccessibilityEvent(ui::AX_EVENT_BLUR, root_);
+  BrowserAccessibilityManager::OnWindowBlurred();
+}
+
 void BrowserAccessibilityManagerWin::NotifyAccessibilityEvent(
     ui::AXEvent event_type,
     BrowserAccessibility* node) {