Always invalidate sticky constraints on the ancestor overflow layer

Always invalidate sticky constraints on the ancestor overflow layer

Previously we only invalidated sticky constraints on the ancestor
overflow layer if the layout object had a paint layer, but we should use
our enclosing layer (which may be the same object, its scroller or
an ancestor with a PaintLayer) to ensure that we invalidate the constraint
within the scroller.

BUG=690580
Review-Url: https://codereview.chromium.org/2683313003
Cr-Commit-Position: refs/heads/master@{#449993}
(cherry picked from commit b65f6264820a5c2e82aa1c9953b37ef34a4d02ec)

Review-Url: https://codereview.chromium.org/2696093003 .
Cr-Commit-Position: refs/branch-heads/2987@{#520}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed: https://chromium.googlesource.com/chromium/src/+/643a0f48f293e0ae53903353b5bb54ed28bb4165

[flackr, 2017-02-15 15:58:36]

Description was changed from

==========
Always invalidate sticky constraints on the ancestor overflow layer

Previously we only invalidated sticky constraints on the ancestor
overflow layer if the layout object had a paint layer, but we should use
our enclosing layer (which may be the same object, its scroller or
an ancestor with a PaintLayer) to ensure that we invalidate the constraint
within the scroller.

BUG=690580

Review-Url: https://codereview.chromium.org/2683313003
Cr-Commit-Position: refs/heads/master@{#449993}
(cherry picked from commit b65f6264820a5c2e82aa1c9953b37ef34a4d02ec)
==========

to

==========
Always invalidate sticky constraints on the ancestor overflow layer

Previously we only invalidated sticky constraints on the ancestor
overflow layer if the layout object had a paint layer, but we should use
our enclosing layer (which may be the same object, its scroller or
an ancestor with a PaintLayer) to ensure that we invalidate the constraint
within the scroller.

BUG=690580

Review-Url: https://codereview.chromium.org/2683313003
Cr-Commit-Position: refs/heads/master@{#449993}
(cherry picked from commit b65f6264820a5c2e82aa1c9953b37ef34a4d02ec)

Review-Url: https://codereview.chromium.org/2696093003 .
Cr-Commit-Position: refs/branch-heads/2987@{#520}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/643a0f48f293e0ae53903353b5bb...
==========

[flackr, 2017-02-15 15:58:38]

Committed patchset #1 (id:1) manually as
643a0f48f293e0ae53903353b5bb54ed28bb4165.