The only places we were using it was for strings that are ASCII anyway,
so this is both more efficient and avoids this Chrome bug:

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