A discussion on embedding WebM files in a forum revealed inconsistent behavior across different operating systems and browsers. miles initially reported issues with embedded WebM clips not working on some systems, despite using the same embedding method.
Miles shared observations of the issue across various OS and browser combinations, with the clip only working on Android 7 using DuckDuckGo.
Codinghorror suggested checking the WebM compatibility using caniuse.com/webm, but the issue persisted despite the browser supporting WebM.
Further investigation by miles revealed that the issue might be related to the http vs https protocol, with the webmshare host’s HTTPS connection not being secure.
Codinghorror confirmed that the issue lies with the specific target site (webmshare) rather than the forum.
Ultimately, miles found a straightforward solution by dragging and dropping the .webm file directly into the forum, which generates a working embedded link.
I checked again and I’m still getting the “No video with supported format and MIME type found” error in Firefox 86 and Chrome 88 for Ubuntu 20.04. Seems like it should be working according to CanIUse.
The errors are slightly different in Firefox and it continues to fail to load after refresh with dev console open. This consistent behavior seems more reasonable:
All candidate resources failed to load. Media load paused.
Seems like a http vs https issue. With the original link (no prefix), it appears to default to http://. Here’s another version that explicitly includes the secure https:// prefix, but that’s not working either.
https://s1.webmshare.com/jvY0A.webm
Appears to be an issue with the webmshare host where their https connection is not actually secure.
