New issue
Advanced search Search tips

Issue 626400 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 647568
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Support for EUC-JP encoding

Reported by addisoni...@gmail.com, Jul 7 2016

Issue description

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-JP, our tests produce 30 errors in Chrome. 

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

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: 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!

[Filed on behalf of W3C I18N WG]
 
Whoops. Pasted the wrong github issue. Correct issue is:

https://github.com/whatwg/encoding/issues/59

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

Components: Blink>TextEncoding

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

Labels: -Cr-ChromeFrame
Status: Available (was: Unconfirmed)

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

Cc: js...@chromium.org

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

Blockedon: 647568

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

Blockedon: -647568
Mergedinto: 647568
Status: Duplicate (was: Available)
Merging to  bug 647568  because there's nothing wrong with the text encoder. The test failure is due to (mis)handling of 30 characters in question. 

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

Blockedon: 647568

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

Blockedon: -647568

Sign in to add a comment