Fix race in BrowserAccessibilityManagerWin creation.
Previously, BrowserAccessibilityManagerWin needed its parent
HWND and parent IAccessible upon construction, and if RWHVA
didn't have those, it didn't create the BAMW. This resulted
in at least two races:
* If an accessibility tree update came from the renderer
but the BAMW wasn't created because the window wasn't available,
the tree update would get discarded - possibly leading to an
assertion failure / renderer crash later on the next update
from being out of sync.
* If we tried to create the BAMW before the LegacyRWHH existed,
we would fall through and create a BAM instead of a BAMW,
making that whole tab inaccessible.
To fix both issues, we always create a BAMW when needed, and
we update the BAMW with the LegacyRWHH as soon as it's
available.
BUG=372478,379019
NOTRY=true
Review URL: https://codereview.chromium.org/329053004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276950 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/content/browser/accessibility/browser_accessibility_manager_win.h b/content/browser/accessibility/browser_accessibility_manager_win.h
index 18260e4f..90914db 100644
--- a/content/browser/accessibility/browser_accessibility_manager_win.h
+++ b/content/browser/accessibility/browser_accessibility_manager_win.h
@@ -40,6 +40,8 @@
parent_iaccessible_ = parent_iaccessible;
}
+ void SetAccessibleHWND(LegacyRenderWidgetHostHWND* accessible_hwnd);
+
// Calls NotifyWinEvent if the parent window's IAccessible pointer is known.
void MaybeCallNotifyWinEvent(DWORD event, LONG child_id);
