Fix missing content issues
When a node is attached, explicitly ensure the parent accessible object for it has ChildrenChanged() called for it, rather than relying on unclear codepaths for this to happen. This regressed in CL:2399317, which altered deferred the work in UpdateCacheAfterNodeIsAttached. Previously, side effects from Get() during dirty layout led to having the parent recompute its children. R=dmazzoni@chromium.org Bug: 1141106 Change-Id: I655784f19668b606b02d1d6ac6e30fbf655cc5c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567228 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#833395}
Showing
Please register or sign in to comment