WebAccessibilityCache is duplicating the functionality of AXObjectCache rather than replacing it.
In addition, it's resulting in a subtle and confusing bug: because it uses a hash from pointer to ID, occasionally an object will be deleted, but another object will be allocated that coincidentally happens to get the same pointer address. When this happens, WebAccessibilityCache gives it the same ID, which can cause all sorts of anomalous behavior.
This bug is to first add the necessary methods to wrap the existing AXObjectCache functionality needed. Then Chromium will be modified to use these methods instead of WebAccessibilityCache. Finally, we'll remove WebAccessibilityCache (https://bugs.webkit.org/show_bug.cgi?id=68224).
Created attachment 107611 [details]
Comment on attachment 107611 [details]
Clearing flags on attachment: 107611
Committed r95491: <http://trac.webkit.org/changeset/95491>
All reviewed patches have been landed. Closing bug.