Improve numeric value handling in CSS Parser

Improve numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.

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

[rwlbuis, 2016-08-01 20:58:33]

Description was changed from

==========
numericValue WIP

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

to

==========
Update numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.
==========

[rwlbuis, 2016-08-01 20:59:15]

Description was changed from

==========
Update numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.
==========

to

==========
Improve numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.
==========

[rwlbuis, 2016-08-02 00:09:27]

rob.buis@samsung.com changed reviewers:
+ timloh@chromium.org

[rwlbuis, 2016-08-02 00:09:27]

PTAL.

[Timothy Loh, 2016-08-02 03:53:58]

On 2016/08/02 00:09:27, rwlbuis wrote:
> PTAL.

lgtm

[rwlbuis, 2016-08-02 10:11:59]

The CQ bit was checked by rob.buis@samsung.com

[commit-bot: I haz the power, 2016-08-02 10:12:19]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-02 12:26:50]

Description was changed from

==========
Improve numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.
==========

to

==========
Improve numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.
==========

[commit-bot: I haz the power, 2016-08-02 12:26:51]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-02 12:28:23]

Description was changed from

==========
Improve numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.
==========

to

==========
Improve numeric value handling in CSS Parser

This patch changes numeric value handling in two ways:
1. Instead of scanning every parsed token for invalid
numeric values, only scan tokens of type NumberToken
by checking the value on token creation.
2. Do not consider out of range numerical values as
invalid but instead clamp to float range.

Several tests are rebased because of the change
listed under 2.

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

[commit-bot: I haz the power, 2016-08-02 12:28:24]

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