Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Video not looping when background is true
See original GitHub issueExpected Behavior
Video should loop when ended if background is set to true
Actual Behavior
Video autoplays like it should but does not loop.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
HTML5 video will not loop - google chrome - Stack Overflow
I was loading an mp4 and a webm file and noticed that the video was not looping in Chrome. It was because the...
Read more >Re: Background video works but does not loop - any...
I have successfully created a background video and it works perfectly. However, at the end of the video it just stops on the...
Read more >Video set to loop doesn't loop when uploaded to server
1. In the HTML5 <video> tag, attributes like controls, autoplay and loop are now boolean. Simply by existing in the video tag, they...
Read more >Background Video with no loop and stop at last scene
I would like to use a Background Video instead. But how can I stop the looping of the video and let the last...
Read more >Prevent background video from looping - YOOtheme Support
Hi sean.butterworth,. unfortunately, it is not a feature of YOOtheme Pro to remove the loop of background videos. You can remove the loop ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This has been fixed in our most recent release. Thank you for logging.
The issue seems to be solved. Thanks a lot 😃.