Streams: Fix exception message for NaN HWM

Streams: Fix exception message for NaN HWM

ReadableStream and WritableStream both used streamErrors.errInvalidHWM
instead of streamErrors.invalidHWM for the message when a strategy
highWaterMark was NaN. This resulted in a RangeError being thrown with
an empty message. Because the web platform tests don't look at the
message, they didn't catch the bug.

Fix the message. Also add a Chromium-specific regression test to
validate that it is correct.

BUG=719763
Review-Url: https://codereview.chromium.org/2933853003
Cr-Commit-Position: refs/heads/master@{#478880}
Committed: https://chromium.googlesource.com/chromium/src/+/7f4a499745ae9a8601e20ef616e8e1e877934269

[Adam Rice, 2017-06-13 00:43:09]

ricea@chromium.org changed reviewers:
+ tyoshino@chromium.org

[tyoshino (SeeGerritForStatus), 2017-06-13 01:06:29]

lgtm

[Adam Rice, 2017-06-13 01:30:27]

The CQ bit was checked by ricea@chromium.org

[commit-bot: I haz the power, 2017-06-13 01:31:01]

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, 2017-06-13 03:15:26]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1497317427070480, "parent_rev":
"1b5feabc7f79238b5a95ab429a5aae55d603100e", "commit_rev":
"7f4a499745ae9a8601e20ef616e8e1e877934269"}

[commit-bot: I haz the power, 2017-06-13 03:15:34]

Description was changed from

==========
Streams: Fix exception message for NaN HWM

ReadableStream and WritableStream both used streamErrors.errInvalidHWM
instead of streamErrors.invalidHWM for the message when a strategy
highWaterMark was NaN. This resulted in a RangeError being thrown with
an empty message. Because the web platform tests don't look at the
message, they didn't catch the bug.

Fix the message. Also add a Chromium-specific regression test to
validate that it is correct.

BUG=719763
==========

to

==========
Streams: Fix exception message for NaN HWM

ReadableStream and WritableStream both used streamErrors.errInvalidHWM
instead of streamErrors.invalidHWM for the message when a strategy
highWaterMark was NaN. This resulted in a RangeError being thrown with
an empty message. Because the web platform tests don't look at the
message, they didn't catch the bug.

Fix the message. Also add a Chromium-specific regression test to
validate that it is correct.

BUG=719763

Review-Url: https://codereview.chromium.org/2933853003
Cr-Commit-Position: refs/heads/master@{#478880}
Committed:
https://chromium.googlesource.com/chromium/src/+/7f4a499745ae9a8601e20ef616e8...
==========

[commit-bot: I haz the power, 2017-06-13 03:15:35]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/7f4a499745ae9a8601e20ef616e8...