GitLab

This patch ensures that we don't try and update assignments if
the layout view is locked in its parent frame.

If the view is locked, it means that we skipped processing prepaint
for it, which means that the contents here might not have the
LocalBorderBoxProperties (created during prepaint). However, the
assignment needs the properties to do its work.

Since the frame walk here is unconditional, there is no need to
keep track of the dirty bit flags, as long as we don't clear the
flags on the compositor itself. This is similar to how the throttling
logic behaves.

R=chrishtr@chromium.org

Bug: 1128790
Change-Id: Ic325b618161c68d5886d0a5c0926cbd29e81d38e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422265
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809314}