I've effectively stopped supporting IE11 for over 2 years now... Every other browser added async function support by the end of April, 2017, nearly 3 years ago. That's where I cutoff.
IE11 shouldn't be supported at this point imho, and I will not make efforts to do so. Supporting IE11 adds complexity and/or bundle sizes that are excessive to support what aren't even that modern of features at this point.
https://gist.github.com/tracker1/8eea53ec700a0fea725123516a30a70a
Windows + Chrome... Not sure what input I could offer... it's like the entire application is rendered three times... scrollbar on the right... I didn't interact much, so unsure if it's from the start or each interaction. It is a bit of an odd behavior... the models for all three seem to be the same as changes in one change the others.
Coll... didn't dig in as I don't have time. Advice below.
These *should* be SVG based with minimal JS and not using any heavy libraries... none of this should add more than a couple kb to your payload. So evaluate what you're using.
I've seen a lot of poor practice in terms of using shared UI libraries, many include far more than they ever should.
Should add a note that for..of over strings will give you surrogate pairs and is the most reliable means of doing so for Unicode sets.
// will only print one line for the pair.
for (const c of '\uD83D\uDE00') {
console.log('-', c);
}
Should add a note that for..of over strings will give you surrogate pairs and is the most reliable means of doing so for Unicode sets. // will only print one line for the pair. for (const c of '\uD83D\uDE00') { console.log('-', c); }