Clamp compositor's top controls shown ratio on commit from main thread.

Clamp compositor's top controls shown ratio on commit from main thread.

The shown_ratio should always be in the range [0,1] and this is enforced when
top controls are scrolled. However, we did not enforce this constraint when a
new value is committed from the main thread. This means that if there's an
existing delta on the compositor's active tree value and the main thread commits
a new base value we can see values of the ratio outside this range and this
causes us to violate some assumptions in DCHECKs.

BUG=622134
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/0223f2f72d17879c727bb6a1915e43931b3e8771
Cr-Commit-Position: refs/heads/master@{#401588}

[bokan, 2016-06-22 22:52:03]

Description was changed from

==========
Clamp compositor's top controls shown ratio on commit from main thread.

The shown_ratio should always be in the range [0,1] and this is enforced when
top controls are scrolled. However, we did not enforce this constraint when a
new value is committed from the main thread. This means that if there's an
existing delta on the compositor's active tree value and the main thread commits
a new base value we can see values of the ratio outside this range and this
causes us to violate some assumptions in DCHECKs.

BUG=622134
==========

to

==========
Clamp compositor's top controls shown ratio on commit from main thread.

The shown_ratio should always be in the range [0,1] and this is enforced when
top controls are scrolled. However, we did not enforce this constraint when a
new value is committed from the main thread. This means that if there's an
existing delta on the compositor's active tree value and the main thread commits
a new base value we can see values of the ratio outside this range and this
causes us to violate some assumptions in DCHECKs.

BUG=622134
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

[bokan, 2016-06-22 22:53:16]

bokan@chromium.org changed reviewers:
+ aelias@chromium.org

[bokan, 2016-06-22 22:53:17]

ptal

[bokan, 2016-06-22 23:11:01]

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

[commit-bot: I haz the power, 2016-06-22 23:11:45]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2090223002/20001

[commit-bot: I haz the power, 2016-06-23 00:09:51]

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

[commit-bot: I haz the power, 2016-06-23 00:09:52]

Dry run: This issue passed the CQ dry run.

[aelias_OOO_until_Jul13, 2016-06-23 00:30:19]

lgtm

[bokan, 2016-06-23 12:32:02]

The CQ bit was checked by bokan@chromium.org

[commit-bot: I haz the power, 2016-06-23 12:32:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2090223002/20001

[commit-bot: I haz the power, 2016-06-23 12:35:15]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-06-23 12:36:21]

Description was changed from

==========
Clamp compositor's top controls shown ratio on commit from main thread.

The shown_ratio should always be in the range [0,1] and this is enforced when
top controls are scrolled. However, we did not enforce this constraint when a
new value is committed from the main thread. This means that if there's an
existing delta on the compositor's active tree value and the main thread commits
a new base value we can see values of the ratio outside this range and this
causes us to violate some assumptions in DCHECKs.

BUG=622134
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

to

==========
Clamp compositor's top controls shown ratio on commit from main thread.

The shown_ratio should always be in the range [0,1] and this is enforced when
top controls are scrolled. However, we did not enforce this constraint when a
new value is committed from the main thread. This means that if there's an
existing delta on the compositor's active tree value and the main thread commits
a new base value we can see values of the ratio outside this range and this
causes us to violate some assumptions in DCHECKs.

BUG=622134
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/0223f2f72d17879c727bb6a1915e43931b3e8771
Cr-Commit-Position: refs/heads/master@{#401588}
==========

[commit-bot: I haz the power, 2016-06-23 12:36:22]

Patchset 2 (id:??) landed as
https://crrev.com/0223f2f72d17879c727bb6a1915e43931b3e8771
Cr-Commit-Position: refs/heads/master@{#401588}