Re: [whatwg/encoding] EUK-kr encoding/decoding support (#62)

> https://bugs.chromium.org/p/chromium/issues/detail?id=626396

Chrome's failure in form submission (note that Chromium passes href test 100%) with 28 (mostly Cf characters : https://goo.gl/HKf47P ) is likely to be caused by Blink's handling of those characters even before they reach the EUC-KR encoder. The encoder does not see them at all, which is why there's empty output. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/62#issuecomment-247523110

Received on Friday, 16 September 2016 05:47:54 UTC