GitLab

One call had some extra logic that was missing from the other
call. Most likely it didn't trigger a bug because it's unlikely we'd
ever have a scenario where the root object's AXRelativeBounds changes
but the root isn't serialized. Still, this is definitely the right
thing to do, and it makes the code in RenderAccessibilityImpl
simpler and more readable.

Bug: 1109081
Change-Id: If4ccb9d5dab5393c9b965af48943161c549fd272
AX-Relnotes: N/A
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314874
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791454}