r12a

For what it's worth, the i18n WG also advises against creating any plain text elements when they may contain translatable text, because it may also be necessary to vary the...

You should also use care when looking at "what websites actually request in forms and how", because i think you'll find plenty of sites that tried to shoe-horn things into...

> Some reasons belong to database design; where street names are CHAR, and house numbers are NUM and VARCHAR was expensive or unavailable There's an example of a pattern we...

I updated the table. Something went wrong with the scoring for Safari in the previous version. Should now reflect reality.

List of bugs raised: - https://bugs.webkit.org/show_bug.cgi?id=159891 - https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8202252/

wrt Safari support for GB 18030 (and probably other encodings), there's a discussion at https://bugs.webkit.org/show_bug.cgi?id=159891 that people following the Encoding issues may be able to help with.

@hsivonen just so you know, i'm still intending to check the above and change the tests (and results) where needed, when i get a moment. Same goes for similar comments...

@hsivonen wrt https://github.com/whatwg/encoding/issues/57#issuecomment-297747386, i have stepped through the conversion for the first two tests you mentioned several times, using the debugger alongside the spec text, and i still come up...

@hsivonen ping wrt https://github.com/whatwg/encoding/issues/57#issuecomment-322540517

List of bugs raised: - https://bugs.webkit.org/show_bug.cgi?id=159892 - https://bugzilla.mozilla.org/show_bug.cgi?id=1285400 - https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8202282/ - https://bugs.chromium.org/p/chromium/issues/detail?id=626406