Update the isolated tree even when there is no client request.
Created attachment 405060 [details] Patch
Comment on attachment 405060 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=405060&action=review > Source/WebCore/accessibility/AXObjectCache.cpp:3196 > + case AXLoadingFinished: can we change this method so it doesn't duplicate the logic in the other updateIsolateTree method? instead do something like void AXObjectCache::updateIsolatedTree(AXCoreObject& object, AXLoadingEvent notification) { if (notification == AXLoadingFinished) updateIsoaltedTree(object, AXChildrenChanged) }
Created attachment 405064 [details] Patch
(In reply to chris fleizach from comment #2) > Comment on attachment 405060 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=405060&action=review > > > Source/WebCore/accessibility/AXObjectCache.cpp:3196 > > + case AXLoadingFinished: > > can we change this method so it doesn't duplicate the logic in the other > updateIsolateTree method? instead do something like > > void AXObjectCache::updateIsolatedTree(AXCoreObject& object, AXLoadingEvent > notification) > { > if (notification == AXLoadingFinished) > updateIsoaltedTree(object, AXChildrenChanged) > } Done as suggested. Also pondered the approach of merging the AXLoadingEvent enum into AXNotification. But don't know why it was added as a separate enum, and it would require more changes. Something perhaps for a later cleanup. Thanks.
Committed r264784: <https://trac.webkit.org/changeset/264784> All reviewed patches have been landed. Closing bug and clearing flags on attachment 405064 [details].
<rdar://problem/66007855>