Hi Barry, thanks for the quick response! Sure I will post my findings 👍

Ping @tunetheweb.com @jakearchibald.com

Ping @firefoxperformance.bsky.social

The final workaround that I came up with is to use combination of these two methods. `.decode()` for Firefox and Safari and `createImageBitmap` for Chrome. Here is the repo with more info and examples github.com/myshov/fastD... I hope it will help browser vendors to resolve problems

One method that works for decoding in Chrome without blocking it is using `createImageBitmap()` with blob as an argument. But unfortunately it doesn’t work well in Firefox

If you think that `image.decode()` should execute off main thread and it should help, you are right. But in Chrome drawImage alwaysh trigger additional decoding even for images that were decoded before

Oh… 🙈

A flag which bans TS features with runtime emit (enums, namespaces, experimental decorators, etc) will come in 5.8 to help people executing TS code via Node.js (or who want to avoid using those features for "reasons").

Really cool demo! Probably this idea can also be applied to a text to create interesting wavy effect on hover

But on serious note I have seen that people use api from twitter to extract text of the tweets on statically generated sites. It’s not perfect solution but it can solve the problem with removed tweets

Screenshots will save the web