Issue metadata
Sign in to add a comment
|
Support for Shift-JIS encoding
Reported by
addisoni...@gmail.com,
Jul 7 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 Steps to reproduce the problem: The W3C I18N WG in concert with WHATWG is testing Encoding specification support. For the encoding Shift-JIS, our tests produce 30 errors in Chrome. See: https://github.com/whatwg/encoding/issues/61 What is the expected behavior? No errors detected. What went wrong? See encoding bug above. Please respond to that issue in whatwg's github. Did this work before? No Chrome version: Channel: n/a OS Version: Flash Version: Shockwave Flash 22.0 r0 Note: this may be an error in the specification or an error in the tests, in which case we'd very much like to know!
,
Jul 25 2016
,
Sep 15 2016
Errors are: U+AD, U+34F, U+200B...U+200F, U+202A...U+202E, U+2060...U+206F, U+3164, U+FFA0
,
Sep 16 2016
,
Sep 18 2016
Better to merge to bug 647568 because the text encoder does not do anything wrong. The test failure is due to (mis)handling of 30 characters in question by form submission.
,
Sep 18 2016
,
Sep 18 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Jul 12 2016