The new version of firefox already supports mp3 decoding; the latest versions of most browsers support decoding mp3; firefox nightly seems to support h264 decoding, so the format battle should be regarded as a victory for h264.
But in order to be compatible with all browsers, flash is essential (the ie family that cannot be discarded). ogg, ogv, mp4, mp3, webm, etc. will coexist for a long time. Like the video on the homepage of Bing, if ua is ie, it will be mp4, and if ua is firefox, it will be ogv.
Currently, the latest versions of all mainstream PC and mobile browsers support the mp3 format. http://html5test.com/compare/feature/audio-mp3.html
In fact, the mp3 format has been popularized on mobile devices for a long time, because the CPU is too weak and can only accept the mp3/mp4 hardware decoding solution.
So you still have to embed some players, which will support a wider range of video types, such as JW Player or GrindPlayer. The limitation of relying on the browser itself to parse videos is indeed quite large.
Mainly because the production companies of each browser are different, and the final standard of html5 has not yet been released, so everyone can support whichever format they like~
The reason for this is that it belongs to the same category as browser compatibility. Different browser kernel support results in different supported formats
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
This form has expired;
The new version of firefox already supports mp3 decoding; the latest versions of most browsers support decoding mp3; firefox nightly seems to support h264 decoding, so the format battle should be regarded as a victory for h264.
But in order to be compatible with all browsers, flash is essential (the ie family that cannot be discarded). ogg, ogv, mp4, mp3, webm, etc. will coexist for a long time. Like the video on the homepage of Bing, if ua is ie, it will be mp4, and if ua is firefox, it will be ogv.
In fact, the mp3 format has been popularized on mobile devices for a long time, because the CPU is too weak and can only accept the mp3/mp4 hardware decoding solution.
So you still have to embed some players, which will support a wider range of video types, such as JW Player or GrindPlayer. The limitation of relying on the browser itself to parse videos is indeed quite large.
Even when using a third-party player, multiple audio files are used to resolve compatibility
Mainly because the production companies of each browser are different, and the final standard of html5 has not yet been released, so everyone can support whichever format they like~
The reason for this is that it belongs to the same category as browser compatibility. Different browser kernel support results in different supported formats