Ignore failure from CreateStdAccessibleObject()
On non-desktop Windows SKUs such as Hololens, CreateStdAccessibleObject() will fail since MSAA is not available. That failure would cause us to exit LegacyRenderWidgetHostHWND::Init() before creating a UI Automation fragment root. Later on, an inbound UI Automation call would ask a web content fragment for its fragment root, we would attempt to look it up and find nothing, and crash. The fix is to ignore the failure from CreateStdAccessibleObject(). There are no subsequent calls in Init() that depended on it succeeding. I also took the opportunity to switch the return value to type void since the only caller wasn't doing anything with this information anyway. Bug: 928811 Change-Id: I11f63139575de131f41733be6f73192c118ec792 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037963 Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com> Reviewed-by:Cliff Smolinsky <cliffsmo@microsoft.com> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#739032}
Showing
Please register or sign in to comment