Home/ Questions/Q 7585533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T19:11:58+00:00

I have a video as a background to a web page, and I am

  • 0

I have a video as a background to a web page, and I am trying to get it to loop. Here is the code:

<video autoplay='true' loop='true' muted='true'>
  <source src='/admin/wallpapers/linked/4ebc66e899727777b400003c' type='video/mp4'></source>
</video>

Even though I have told the video to loop, it does not. I also tried to get it to loop with the onended attribute (as per this Mozilla support thread, I also tried that bit of jQuery). Nothing has worked so far. Is it an issue with Chrome, or my code?

Edit:

I checked the Network events and HEAD of a working copy (http://fhsclock-labs.heroku.com/no-violence) versus the application I’m trying to get working. The difference is the working copy is serving up the video from a static asset on Heroku (via Varnish, apparently), whilst mine is serving from GridFS (MongoDB).

The Network tab of Chrome’s Inspector show that in my application, the video is requested three times. One time the Status is “pending”, the second is “canceled”, and the final one is 200 OK. The working copy only shows two requests, one’s Status is pending and the other is 206 Partial Content. However, after the video plays once, that request changes to “Cancelled” and it makes another request for that video. In my application, that does not happen.

As for Type, in my application, two are “undefined” and the other “video/mp4” (which it is supposed to be). In the working app, all of the requests are “video/mp4”.

In addition, I’m getting Resource interpreted as Other but transferred with MIME type undefined. warnings in the Console.

I’m not really quite sure where to begin on this. It’s my belief that the issue is server-side, as serving the file as static assets works fine. It could be that the server isn’t sending the correct content type. It could be an issue with GridFS. I do not know.

At any rate, the source is here. Any insight that you can offer is appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Ah, I just stumbled into this exact problem.

    As it turns out, looping (or any sort of seeking, for that matter) in <video> elements on Chrome only works if the video file was served up by a server that understands partial content requests. i.e. the server needs to honor requests that contain a “Range” header with a 206 “Partial Content” response. This is even the case if the video is small enough to be fully buffered by chrome, and no more server-round trips are made: if your server didn’t honor chrome’s Range request the first time, the video will not be loopable or seekable.

    So yes, an issue with GridFS, although arguably Chrome should be more forgiving.

    • 0