DescriptionFix 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
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276950
Patch Set 1 #
Total comments: 1
Patch Set 2 : Simpler fix #
Total comments: 2
Patch Set 3 : Rebase #
Messages
Total messages: 14 (0 generated)
|