Ensure Layers have valid sequence numbers for PropertyTrees

Ensure Layers have valid sequence numbers for PropertyTrees

Calling Layer::set_property_tree_sequence_number() does not set the
flag that a commit is needed, which means it can quickly get out of
date for layers that are not updated for other reasons when the Layer
is (de)serialized.

This CL makes the LayerTreeHost forcefully set the sequence number
to the same value as the current PropertyTrees.sequence_number, since
all valid in the hierarchy is valid at that point.

BUG=577352, 538710
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/b36e0d5d5100b55128ed7a2c7642afd3591a4e07
Cr-Commit-Position: refs/heads/master@{#371654}

[nyquist, 2016-01-14 23:22:13]

Description was changed from

==========
Ensure Layers have valid sequence numbers for PropertyTrees

Calling Layer::set_property_tree_sequence_number() does not set the
flag that a commit is needed, which means it can quickly get out of
date for layers that are not updated for other reasons when the Layer
is (de)serialized.

This CL makes the LayerTreeHost forcefully set the sequence number
to the same value as the current PropertyTrees.sequence_number, since
all valid in the hierarchy is valid at that point.

BUG=577352, 538710
==========

to

==========
Ensure Layers have valid sequence numbers for PropertyTrees

Calling Layer::set_property_tree_sequence_number() does not set the
flag that a commit is needed, which means it can quickly get out of
date for layers that are not updated for other reasons when the Layer
is (de)serialized.

This CL makes the LayerTreeHost forcefully set the sequence number
to the same value as the current PropertyTrees.sequence_number, since
all valid in the hierarchy is valid at that point.

BUG=577352, 538710
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

[nyquist, 2016-01-14 23:22:25]

The CQ bit was checked by nyquist@chromium.org to run a CQ dry run

[nyquist, 2016-01-14 23:22:37]

nyquist@chromium.org changed reviewers:
+ dtrainor@chromium.org, vmpstr@chromium.org

[nyquist, 2016-01-14 23:22:37]

vmpstr, dtrainor: PTAL

[commit-bot: I haz the power, 2016-01-14 23:22:49]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1584653004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1584653004/1

[commit-bot: I haz the power, 2016-01-15 00:30:47]

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

[commit-bot: I haz the power, 2016-01-15 00:30:47]

Dry run: This issue passed the CQ dry run.

[David Trainor- moved to gerrit, 2016-01-20 17:04:08]

lgtm

[vmpstr, 2016-01-26 22:41:25]

lgtm

[nyquist, 2016-01-26 22:51:21]

The CQ bit was checked by nyquist@chromium.org

[commit-bot: I haz the power, 2016-01-26 22:54:29]

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

[commit-bot: I haz the power, 2016-01-27 00:17:41]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-27 00:18:38]

Description was changed from

==========
Ensure Layers have valid sequence numbers for PropertyTrees

Calling Layer::set_property_tree_sequence_number() does not set the
flag that a commit is needed, which means it can quickly get out of
date for layers that are not updated for other reasons when the Layer
is (de)serialized.

This CL makes the LayerTreeHost forcefully set the sequence number
to the same value as the current PropertyTrees.sequence_number, since
all valid in the hierarchy is valid at that point.

BUG=577352, 538710
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

to

==========
Ensure Layers have valid sequence numbers for PropertyTrees

Calling Layer::set_property_tree_sequence_number() does not set the
flag that a commit is needed, which means it can quickly get out of
date for layers that are not updated for other reasons when the Layer
is (de)serialized.

This CL makes the LayerTreeHost forcefully set the sequence number
to the same value as the current PropertyTrees.sequence_number, since
all valid in the hierarchy is valid at that point.

BUG=577352, 538710
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/b36e0d5d5100b55128ed7a2c7642afd3591a4e07
Cr-Commit-Position: refs/heads/master@{#371654}
==========

[commit-bot: I haz the power, 2016-01-27 00:18:39]

Patchset 1 (id:??) landed as
https://crrev.com/b36e0d5d5100b55128ed7a2c7642afd3591a4e07
Cr-Commit-Position: refs/heads/master@{#371654}