commit ddeb718a9e2a9ec333f64cb8e1cacfea872e4f80
author Javier Contreras <javiercon@microsoft.com> Fri Oct 28 18:00:47 2022
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Fri Oct 28 18:00:47 2022
tree 45dcb63339241b9760381a4762557e9867e55285
parent d611204758d9f5e417890d345b2d06f7803019c6

[ViewsAX] Moving applicable ParentConnection logic up to AXTreeManager

In this CL we've continued moving logic from
BrowserAccessibilityManager up to AXTreeManager as part of the
refactoring. This way, ViewsAXTreeManager will be able to
use the same logic and functions. In this specific case, we move the
non web content specific logic on ParentConnectionChanged from
BrowserAccessibilityManager to AXTreeManager, leaving the override for
web content specific logic on BrowserAccessibilityManager.
As a result of this, there is some duplicate logic that must remain
in both places, since the implementation on
BrowserAccessibilityManager does some work on notifying
BrowserAccessibility objects and AXTreeManager does not have
access to this.

Bug: 1049261
Change-Id: Idd42f895dcfdfbbf60231b63fd2bf48a2fde6f99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3967817
Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
Commit-Queue: Javier Contreras <javiercon@microsoft.com>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1064925}