Mathias Bynens

> However, the ES6 spec says that Unicode 5.1.0 or later is followed, which means that U+0085 and U+200B must be considered non-trimmable, while U+180E may be considered non-trimmable. U+180E...

> Then this means this shim is specifically targeting 5.1.0, thanks for letting me know. The ES6 spec is, and this shim aims to follow that. Thanks for bringing this...

> I'm not sure we should rely on the `u` flag being available for regexes. I never said we should! That wouldn’t work in any existing browser. I was suggesting...

I agree that the many small little files are not very practical to work with as a test author. But I can see why this is unlikely to change. What’s...

It’d be impossible using only CSS, as there’s no way to select text nodes without referring to a wrapper element.

@bravedick Wouldn’t that also apply to text in ``s?

@bravedick Blinks in Firefox.

CC @MylesBorins is this something you could help with? This project has become critical infrastructure for TC39. Perhaps it could get some additional gh-pages space?

> Didn't get around to analyze what makes this one special. Possibly related to the issue in the library you're using mathiasbynens/emoji-regex#28 Yeah, that’s likely the issue. emoji-regex follows the...

What makes you say that it’s been a de facto standard since **ES5** as opposed to ES3/ES2/ES1?