summaryrefslogtreecommitdiffstats
path: root/sync/internal_api/sync_backup_manager.h
diff options
context:
space:
mode:
authordmazzoni@chromium.org <dmazzoni@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-04-21 18:07:29 +0000
committerdmazzoni@chromium.org <dmazzoni@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2014-04-21 18:07:29 +0000
commitd96f384cf58a669efd1637416ed96633a71f4fa5 (patch)
tree360e563be3eec2f139e9a13e4667077b3b58f867 /sync/internal_api/sync_backup_manager.h
parent3087b9eee590b9455084a41aeaf07df156e9bc6a (diff)
downloadchromium_src-d96f384cf58a669efd1637416ed96633a71f4fa5.zip
chromium_src-d96f384cf58a669efd1637416ed96633a71f4fa5.tar.gz
chromium_src-d96f384cf58a669efd1637416ed96633a71f4fa5.tar.bz2
Make BrowserAccessibilityManager use AXTree (re-land).
This is the final step of migrating content/*/accessibility to make full use of the new infrastructure in ui/accessibility. Previously, BrowserAccessibilityManager owned the tree of BrowserAccessibility objects and handled making changes to the tree in response to messages from the renderer. Now, AXTree handles the updates from the renderer and notifies BrowserAccessibilityManager (via AXTreeDelegate) when it should create or destroy BrowserAccessibility objects, and when it should notify a BrowserAccessibility object that it's been modified. This makes the serialization/unserialization logic fully tested now, and greatly clarifies the semantics of when in the update cycle various notifications are called (e.g., PreInitialize and PostInitialize are now OnDataChanged and OnUpdateFinished). BUG=316726 NOTRY=true Review URL: https://codereview.chromium.org/234723003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@265021 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/internal_api/sync_backup_manager.h')
0 files changed, 0 insertions, 0 deletions