www.uidaho.edu - Unable to play videos
URL: https://www.uidaho.edu/engr/programs/eo/explore/demo-a-course-session
Browser / Version: Firefox 103.0.2 Operating System: Mac OS X 12.5 Tested Another Browser: Yes Chrome
Problem type: Video or audio doesn't play Description: There is no video Steps to Reproduce: Click on any video on the page and get a No video with supported format and MIME type found. Used to work in old versions of Firefox.
Browser Configuration
- None
From webcompat.com with ❤️
Thanks for the report, I was able to reproduce the issue.

Console:

Note:
- The issue is not reproducible on Chrome.
- The issue is reproducible on Firefox regardless of the ETP status.
Tested with: Browser / Version: Firefox Nightly 105.0a1 (2022-08-09), Firefox Release 103.0.2 Operating System: Mac OS Monterey v.12.1
Moving to Needsdiagnosis for further investigation.
[qa_32/2022]
I noticed in Chrome we have a source element inside the video tag but in Firefox we don't. Could be our internal code too... investigating that as well. If I put the <source src="https://eo.uidaho.edu/media/CE%20484%20SP%2022.mp4" type="video/mp4"> tag inside the Video tag in the dev tools then the video works. Thank you.
This technically would be a priority p2, but let's bump it to the higest, p1, because we have the developer here in this bug. :) Thanks for filing, @xicubed!
@xicubed, after using mozregression and chatting with the relevant folks, we've narrowed this down to https://bugzilla.mozilla.org/show_bug.cgi?id=1781759, the fix for which is under review and should hopefully make it into Firefox over the next version or two.
In the meantime, it seems that working around this would require either not serving videos from the same origin or by not using an iframe, but just a video element. Is there a specific reason why they must be served from an iframe like this?
To clarify/correct: Using a video element would work either cross- or same-origin. Our bug means that video sources loaded as documents into iframes will usually only play when same-origin.
There is a third possible workaround, but it may have unintended consequences: Adding the "Content-Security-Policy: sandbox" header to the video source will happen to allow the video to play in an iframe when cross-origin, but a related bug means this would then not play with this header when same-origin in an iframe or as a toplevel load.
I know that sounds very confused. It is. The video should play fine in an iframe. I am curious as to the reason for the choice of an iframe though?
@karlt I mean at some level the iframe is there because that's the way the CMS vendor Sitecore chose to handle embeds. We basically fill out a form and it handles the code. Furthermore I think our university also has a shim or wrapper or something maybe to modify the player or something. I'm not affiliated with that group but I'm working through a support wing. More confusing is that the support guy did a couple more embeds for us and they work in Firefox. See https://www.uidaho.edu/engr/programs/eo/student-orientation. He is going to see if he can spot differences when he gets a chance as will I.
Also we could put the video on the same site in theory, it's just they're trying to dissuade users from doing that as they don't want to be in the video hosting business. Most people just embed YouTube for video.
More confusing is that the support guy did a couple more embeds for us and they work in Firefox. See https://www.uidaho.edu/engr/programs/eo/student-orientation.
Unfortunately, even those will probably not play reliably. The Portal Tour failed mid-playback for me one time. Whether our bug comes into play depends on whether a second network request is performed for the video resource. Smaller videos are more likely to load in one request and so be unaffected. Cache effects can come into play too.
The video would play fine from a <video> element in a small wrapper html document loaded into the iframe, in case that's an option.
There is some good news here: I've just confirmed that the fix I mentioned earlier does the trick here, as the videos are working on today's nightly builds of Firefox. So at least this ought to be fixed in Firefox 105, even if we can't find a work around for earlier versions.
I can confirm it is no longer reproducible on Firefox Nightly 106, and indeed still occurs on Firefox Release 104.

Tested with: Browser / Version: Firefox Nightly 106.0a1 (2022-08-29) Operating System: Windows 10 Pro
[inv_35/2022]