For manual testing purposes, we should have the ability to log instances when the value the AT receives from the cache differs from the computed value in content. We can't use sync calls because that isn't allowed on Windows, so the actual comparison happens in the content process using an async call from parent with the cache payload.

This is a very crude cache review method, and there will be plenty of false positives since the state of content/parent is not guaranteed to be synced.

For example, if run with a browser e10s name test, it will flag a lot mismatches because the content is always one state ahead of parent. Nonetheless, this already helped me find a bug where we were inadvertently storing DeleteEntry values.

Backed out changeset a6d7f0da2513 (Bug 1729061) for causing bustages on DocAccessibleChildBase.cpp.
Backout link
Push with failures H
Failure Log

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:eeejay, could you have a look please?
For more information, please visit auto_nag documentation.

Backed out changeset 4d44c5b706db (Bug 1729061) for causing bustages in DocAccessibleChildBase.cpp. CLOSED TREE

Push with failures: https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&collapsedPushes=842382&selectedTaskRun=VSLJudhJS92i0qhZE0EhxA.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=4d44c5b706db15a721cc612dfa5236b9af513d21

Log: https://treeherder.mozilla.org/logviewer?job_id=352865396&repo=autoland&lineNumber=13226

Backout: https://hg.mozilla.org/integration/autoland/rev/b30a8b1386be51de76a5f65c482e65d7ebef56fa

https://hg.mozilla.org/mozilla-central/rev/976f1b8e7f85