Andrea Giammarchi

IIRC for backward compability this has been a well known exception in the normalization logic.

shouldn't a favicon be just a `favicon.ico` since that's what browsers would expect by default anyway? This is also quite huge, old browsers unfriendly .

Better now. We need a `favicon.ico` file name on the root of the site. Such `.ico` should possibly be at least 32x32 px and ideally with multiple resolutions such: 16x16,...

Nope, that doesn't work. If it does it's a webpack bug. You cannot reference something directly if not defined already so that OR is a reference error if global is...

> It's a runtime behaviour, webpack has nothing to do with it it's broken code. Write this in console: ```js var failure = nope || window; ``` And admire the...

is such JSON inside a script tag on the page? twemoji itself doesn't change anything automatically, so it'd be weird to hear about this

So, as you can see, script nodes are not parsed: https://github.com/twitter/twemoji/blob/master/scripts/generate#L264 This means you are parsing strings instead of creating proper nodes, and I suggest you use a template tag...

can this be automated and compatible with Twemoji license? If Yes, PR welcome, if Not you can go ahead and host those new files and configure the JS library to...

The parser replaces occurrences of emoji with `` tags, pointing at the related file. Pseudo elements are not replaceable using the same technique, neither discoverable with ease, unless you check...

this is the most horrifying Firefox bug I've ever seen to date: https://codepen.io/WebReflection/pen/WXaeWj?editors=0010