Don't explicitly initialize LayoutUnit to 0.

Don't explicitly initialize LayoutUnit to 0.

The default LayoutUnit() constructor sets it to 0. Explicitly passing 0 means
that LayoutUnit::setValue() will be involved, which performs (in this case:
very pointless) saturation checks.

Committed: https://crrev.com/3e0d01bb6765429ee3d2347337e1c8a490bd1165
Cr-Commit-Position: refs/heads/master@{#396223}

[mstensho (USE GERRIT), 2016-05-26 11:38:31]

mstensho@opera.com changed reviewers:
+ eae@chromium.org

[svillar, 2016-05-26 14:33:26]

svillar@igalia.com changed reviewers:
+ svillar@igalia.com

[svillar, 2016-05-26 14:33:26]

lgtm

[eae, 2016-05-26 17:25:46]

LGTM

[mstensho (USE GERRIT), 2016-05-26 17:47:56]

The CQ bit was checked by mstensho@opera.com

[commit-bot: I haz the power, 2016-05-26 17:48:14]

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

[commit-bot: I haz the power, 2016-05-26 17:53:05]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-05-26 17:54:14]

Description was changed from

==========
Don't explicitly initialize LayoutUnit to 0.

The default LayoutUnit() constructor sets it to 0. Explicitly passing 0 means
that LayoutUnit::setValue() will be involved, which performs (in this case:
very pointless) saturation checks.
==========

to

==========
Don't explicitly initialize LayoutUnit to 0.

The default LayoutUnit() constructor sets it to 0. Explicitly passing 0 means
that LayoutUnit::setValue() will be involved, which performs (in this case:
very pointless) saturation checks.

Committed: https://crrev.com/3e0d01bb6765429ee3d2347337e1c8a490bd1165
Cr-Commit-Position: refs/heads/master@{#396223}
==========

[commit-bot: I haz the power, 2016-05-26 17:54:15]

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