Pass nullptr for paintInvalidationState if it can't be used to map geometry.

Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Therefore, after it returning false for canMapToAncestor(), pass nullptr fur
further recursions up the layout tree.

Furthermore, using it for an ancestor is invalid because a
PaintInvalidationState object is bound to a single LayoutObject.

Also adds PaintInvalidationState early-outing to LayoutView.

BUG=594516
Committed: https://crrev.com/4e57e854bd3a3e47c4aa18ce934d838e4eed4030
Cr-Commit-Position: refs/heads/master@{#382772}

[chrishtr, 2016-03-22 02:40:44]

Description was changed from

==========
none


none

BUG=
==========

to

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Furthermore, using it for an ancestor is invalid because the
PaintInvalidationState
is bound to a single LayoutObject.

BUG=594516
==========

[chrishtr, 2016-03-22 02:41:07]

Description was changed from

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Furthermore, using it for an ancestor is invalid because the
PaintInvalidationState
is bound to a single LayoutObject.

BUG=594516
==========

to

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Furthermore, using it for an ancestor is invalid because the
PaintInvalidationState
is bound to a single LayoutObject.

Also adds PaintInvalidationState early-outing to LayoutView.

BUG=594516
==========

[chrishtr, 2016-03-22 02:42:16]

Description was changed from

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Furthermore, using it for an ancestor is invalid because the
PaintInvalidationState
is bound to a single LayoutObject.

Also adds PaintInvalidationState early-outing to LayoutView.

BUG=594516
==========

to

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Therefore, after it returning false for canMapToAncestor(), pass nullptr fur
further recursions up the layout tree.

Furthermore, using it for an ancestor is invalid because a
PaintInvalidationState object is bound to a single LayoutObject.

Also adds PaintInvalidationState early-outing to LayoutView.

BUG=594516
==========

[chrishtr, 2016-03-22 02:43:08]

chrishtr@chromium.org changed reviewers:
+ wangxianzhu@chromium.org

[chrishtr, 2016-03-22 02:43:09]

I found this when working on the referenced bug.

[Xianzhu, 2016-03-22 16:41:40]

LGTM.

I'm working on a bigger change to move all fast path paint invalidation mapping
code into PaintInvalidationState, which removes the optional parameter.
Hopefully it'll be ready for review in today or tomorrow. For preview:
https://codereview.chromium.org/1813383002.

[chrishtr, 2016-03-22 17:55:28]

The CQ bit was checked by chrishtr@chromium.org

[chrishtr, 2016-03-22 17:55:29]

The patchset sent to the CQ was uploaded after l-g-t-m from
wangxianzhu@chromium.org
Link to the patchset: https://codereview.chromium.org/1818963003/#ps40001
(title: " ")

[commit-bot: I haz the power, 2016-03-22 17:55:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1818963003/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1818963003/40001

[chrishtr, 2016-03-22 17:55:54]

Turns out PaintInvalidationState doesn't work yet for LayoutView, added a TODO
for that.

[commit-bot: I haz the power, 2016-03-22 20:59:28]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-22 20:59:29]

Try jobs failed on following builders:
  linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[chrishtr, 2016-03-23 01:10:24]

The CQ bit was checked by chrishtr@chromium.org

[commit-bot: I haz the power, 2016-03-23 01:11:01]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1818963003/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1818963003/40001

[commit-bot: I haz the power, 2016-03-23 02:18:05]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-03-23 02:19:44]

Description was changed from

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Therefore, after it returning false for canMapToAncestor(), pass nullptr fur
further recursions up the layout tree.

Furthermore, using it for an ancestor is invalid because a
PaintInvalidationState object is bound to a single LayoutObject.

Also adds PaintInvalidationState early-outing to LayoutView.

BUG=594516
==========

to

==========
Pass nullptr for paintInvalidationState if it can't be used to map geometry.

If it can't be used for the current object, it can't be used for an ancestor.
Therefore, after it returning false for canMapToAncestor(), pass nullptr fur
further recursions up the layout tree.

Furthermore, using it for an ancestor is invalid because a
PaintInvalidationState object is bound to a single LayoutObject.

Also adds PaintInvalidationState early-outing to LayoutView.

BUG=594516

Committed: https://crrev.com/4e57e854bd3a3e47c4aa18ce934d838e4eed4030
Cr-Commit-Position: refs/heads/master@{#382772}
==========

[commit-bot: I haz the power, 2016-03-23 02:19:45]

Patchset 3 (id:??) landed as
https://crrev.com/4e57e854bd3a3e47c4aa18ce934d838e4eed4030
Cr-Commit-Position: refs/heads/master@{#382772}