2 ms·

So it turned out that Chrome 93-95 had a weird issue with the video element: you couldn't replace the source attribute reliably. Unfortunately, that's something

by tgv 4y ago

So it turned out that Chrome 93-95 had a weird issue with the video element: you couldn't replace the source attribute reliably. Unfortunately, that's something that mattered to us, so I had a hack in place that tested the browser version. It's still there in case someone hasn't updated their browser. Testing the feature was simply not possible. It was either that or just let (a large) part of our users get stuck on a frozen screen.

Pathogen-David 4y ago
Yup, the "test for feature availability" attitude doesn't properly account for features which are available yet buggy. I recently ran into an issue where a media-heavy blog post of mine would sporadically crash iOS Safari. I ended up narrowing it down to my use of ImageBitmap to accelerate rendering images into 2D canvases on the page. My fix ended up being to modify my ImageBitmap feature check to pretend it wasn't supported on Safari.