The web implementation of video_player.
This package is endorsed, which means you can simply use video_player normally. This package will be automatically included in your app when you do.
Video playback on the Web platform has some limitations that might surprise developers more familiar with mobile/desktop targets.
In no particular order:
The web platform does not suppport dart:io, so attempts to create a VideoPlayerController.file will throw an UnimplementedError.
Attempts to start playing videos with an audio track (or not muted) without user interaction with the site (“user activation”) will be prohibited by the browser and cause runtime errors in JS.
See also:
Certain videos will rewind to the beginning when users attempt to seekTo (change the progress/scrub to) another position, instead of jumping to the desired position. Once the video is fully stored in the browser cache, seeking will work fine after a full page reload.
The most common explanation for this issue is that the server where the video is stored doesn't support HTTP range requests.
NOTE: Flutter web's local server (the one that powers
flutter run) DOES NOT support range requests, so all video assets indebugmode will exhibit this behavior.
See Issue #49360 for more information on how to diagnose if a server supports range requests or not.
The VideoPlayerOptions.mixWithOthers option can't be implemented in web, at least at the moment. If you use this option it will be silently ignored.
Different web browsers support different sets of video codecs.
Check MDN's Web video codec guide to learn more about the pros and cons of each video codec.
Visit caniuse.com: ‘video format’ for a breakdown of which browsers support what codecs. You can customize charts there for the users of your particular website(s).
Here's an abridged version of the data from caniuse, for a Global audience:
