This is starting to feel like the IE6 situation.

1. Someone comes up with a cool feature.

2. Browser developer refuses to incorporate it since "No one uses it!". Pushes developed in-house technology instead.

3. No one uses the feature as a result. "See no one wants it!"

4. Competitors start to implement the feature

5. ???

And no, pollyfill is again not the (right) solution.

A polyfill (in the form of a wasm blob that implements the decoder) would be an interesting solution at least, since it would make the chrome experience noticeably worse than any competitor that has native support.