uhm, wat?
7
6
1
28
Please don’t @ me, I know what a Unicode is.
4
2
1
34
wait, what's the answer?
1
unicode :( i think I had two different kinds of à
2
3
and i’m getting one of the strings from an element’s textContent, and the other from a hardcoded string so I’m calling shenanigans.
2
2
I believe this is theoretically what string.normalize() is supposed to help with.
1
2
i’m on IE11 :(((((
1
4
Unfortunately one of Unicode's requirements was "do everything legacy encodings can do" (no matter how awful)
1
Hopefully making sure both strings are NFC will fix it? We came close to a Web-wide fix a few years ago...
1
... but it seemed to scary for compatibility. (Some i18n WG folks wanted comparison-time normalization, ...
1
Replying to @davidbaron @notwaldorf @domenic @__apf__
... but I thought it was much saner to do a normalization pass after decoding, but still too risky for compat)

Mar 2, 2017 · 12:52 AM UTC
1