New issue
Advanced search Search tips

Issue 626396 link

Starred by 3 users
Status: Duplicate
Merged: issue 647568
Owner: ----
Closed: Sep 2016
Cc:
js...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Support for EUC-KR encoding

Reported by addisoni...@gmail.com, Jul 7 2016 
UserAgent: 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 EUC-KR, our tests produce 28 errors in Chrome. 

See: https://github.com/whatwg/encoding/issues/62 

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: <Copy from: 'about:version'>  Channel: n/a
OS Version: 
Flash Version: 

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!

Comment 1 by ajha@chromium.org, Jul 12 2016

Components: Blink>TextEncoding

Comment 2 by jsb...@chromium.org, Jul 25 2016

Cc: js...@chromium.org
Labels: -Cr-ChromeFrame
Status: Available (was: Unconfirmed)

Comment 3 by jsb...@chromium.org, Sep 15 2016 

Errors are:

U+34F, U+200B...U+200F, U+202A...U+202E, U+2060...U+206F, U+FFA0

Comment 4 by js...@chromium.org, Sep 16 2016 

They're not covered by EUC-KR and are supposed to be represented with NCRs. 

Those characters pass in href test, but fail in form encoding test. 

jsbell@: do you have any idea why 'form' test fails? Could it be the same reason as gb18030 fails form test?

Comment 5 by js...@chromium.org, Sep 16 2016

Components: Blink>Forms>Text

See https://goo.gl/HKf47P for the identities of characters in comment 3.  They're mostly Cf and default-ignorable. 

U+200B .. U+200F are all format controls (ZWSP, ZWJ, ZWNJ, LRM, RLM). 
U+202E: RLE
U+2060 ... 206F: invisible... ...
U+034F : CGJ
U+FFA0: Half-width Hangul filler. 

It''s more likely to be a form submission  or text issue. Or, it could be an HTML parsing issue. I suspect that those characters would not even be seen by the EUC-KR encoder (fromUnicode).

Comment 6 by js...@chromium.org, Sep 16 2016

Blockedon: 647568

Comment 7 by js...@chromium.org, Sep 16 2016 

The set has actually 30 characters ( https://goo.gl/MJic9t ).

Comment 8 by tkent@chromium.org, Sep 16 2016

Components: -Blink>Forms>Text

Comment 9 by js...@chromium.org, Sep 18 2016

Components: -Blink>TextEncoding Blink>Forms>Submission
Labels: OS-All
Mergedinto: 647568
Status: Duplicate (was: Available)
It's better merge this to  bug 647568  because W3C test failure has nothing to do with Text encoder but is due to a form submission handling of 30 characters in question.

Comment 10 by js...@chromium.org, Sep 18 2016

Blockedon: -647568
►

Sign in to add a comment