Fix a munged Shift-JIS layout test file

Fix a munged Shift-JIS layout test file

fast/encoding/invalid-multi-byte-over-consumption.html is supposed to
have a sequence of '0x83 0x22' (an invalid sequence in Shift_JIS), but
it's somehow changed to '0xEF 0xBF 0xBD' (UTF-8 representation of
U+FFFD - replacement characters) followed by 0x22.

The whole point of this test is to make sure that only the first byte (0x83)
of a 'two-byte invalid sequence' is consumed and the second byte (0x22) is
interpreted as U+0022. So, having '0xEF 0xBF 0xBD' defeats the purpose of
this test.

Note that this file has to be landed manually because rietveld cannot
handle a non-UTF-8 text file.

BUG=597517
TEST=the above layout test.
TBR=dpranke@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/b03c4cbfe2ae0a323ea5c4c5ce56d1e336f095cf

[jungshik at Google, 2016-04-01 09:29:24]

Sorry to bother you. Review is not possible in riedvelt because it involves a
non-UTF-8 file. I'm gonna land directly, but this CL is uploaded here for the
record.

[commit-bot: I haz the power, 2016-04-01 09:33:21]

Description was changed from

==========
Fix a munged Shift-JIS layout test file

fast/encoding/invalid-multi-byte-over-consumption.html is supposed to
have a sequence of '0x83 0x22' (an invalid sequence in Shift_JIS), but
it's somehow changed to '0xEF 0xBF 0xBD' (UTF-8 representation of
U+FFFD - replacement characters) followed by 0x22.

The whole point of this test is to make sure that only the first byte (0x83)
of a 'two-byte invalid sequence' is consumed and the second byte (0x22) is
interpreted as U+0022. So, having '0xEF 0xBF 0xBD' defeats the purpose of
this test.

Note that this file has to be landed manually because rietveld cannot
handle a non-UTF-8 text file.

BUG=597517
TEST=the above layout test.
TBR=dpranke@chromium.org
==========

to

==========
Fix a munged Shift-JIS layout test file

fast/encoding/invalid-multi-byte-over-consumption.html is supposed to
have a sequence of '0x83 0x22' (an invalid sequence in Shift_JIS), but
it's somehow changed to '0xEF 0xBF 0xBD' (UTF-8 representation of
U+FFFD - replacement characters) followed by 0x22.

The whole point of this test is to make sure that only the first byte (0x83)
of a 'two-byte invalid sequence' is consumed and the second byte (0x22) is
interpreted as U+0022. So, having '0xEF 0xBF 0xBD' defeats the purpose of
this test.

Note that this file has to be landed manually because rietveld cannot
handle a non-UTF-8 text file.

BUG=597517
TEST=the above layout test.
TBR=dpranke@chromium.org

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

[commit-bot: I haz the power, 2016-04-01 09:33:22]

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

[jungshik at Google, 2016-04-01 09:34:03]

Description was changed from

==========
Fix a munged Shift-JIS layout test file

fast/encoding/invalid-multi-byte-over-consumption.html is supposed to
have a sequence of '0x83 0x22' (an invalid sequence in Shift_JIS), but
it's somehow changed to '0xEF 0xBF 0xBD' (UTF-8 representation of
U+FFFD - replacement characters) followed by 0x22.

The whole point of this test is to make sure that only the first byte (0x83)
of a 'two-byte invalid sequence' is consumed and the second byte (0x22) is
interpreted as U+0022. So, having '0xEF 0xBF 0xBD' defeats the purpose of
this test.

Note that this file has to be landed manually because rietveld cannot
handle a non-UTF-8 text file.

BUG=597517
TEST=the above layout test.
TBR=dpranke@chromium.org

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

to

==========
Fix a munged Shift-JIS layout test file

fast/encoding/invalid-multi-byte-over-consumption.html is supposed to
have a sequence of '0x83 0x22' (an invalid sequence in Shift_JIS), but
it's somehow changed to '0xEF 0xBF 0xBD' (UTF-8 representation of
U+FFFD - replacement characters) followed by 0x22.

The whole point of this test is to make sure that only the first byte (0x83)
of a 'two-byte invalid sequence' is consumed and the second byte (0x22) is
interpreted as U+0022. So, having '0xEF 0xBF 0xBD' defeats the purpose of
this test.

Note that this file has to be landed manually because rietveld cannot
handle a non-UTF-8 text file.

BUG=597517
TEST=the above layout test.
TBR=dpranke@chromium.org

Committed:
https://chromium.googlesource.com/chromium/src/+/b03c4cbfe2ae0a323ea5c4c5ce56...
==========

[jungshik at Google, 2016-04-01 09:34:05]

Committed patchset #1 (id:1) manually as
b03c4cbfe2ae0a323ea5c4c5ce56d1e336f095cf (presubmit successful).

[Dirk Pranke, 2016-04-01 16:59:02]

lgtm.