Repository metrics
- Stars
- (4,488 個のスター)
- PR merge metrics
- (平均マージ 2d) (30d で 9 merged PRs)
説明
From what I saw, most developers prefer third-party players (video.js, Plyr, etc.) over native <video> and <audio> elements for two reasons:
- style player
- add controls
Off the top of my head:
-
The speed of the audio/video playback can be set only via
playbackRateproperty:document.getElementById('player').playbackRate = 0.5. Why not to expose it as UI control? -
Whether the audio/video should start playing over again when it's finished can be set only via
loopproperty:document.getElementById('player').loop = trueor vialoopattribute:<video src="test.webm" loop>. Why not to expose it as UI control? -
There's no UI for switching sources (e.g. audio sources in different languages, video sources in different resolutions).
-
The
<source>element has nosrclangandlabelattrubutes unlike<track>element. You can't do something like:
<video width="320" height="240" controls>
<source src="forrest_gump_480.mp4" type="video/mp4" label="480p">
<source src="forrest_gump_1080.mp4" type="video/mp4" label="1080p" default>
<source src="forrest_gump_en.ogg" type="audio/ogg" srclang="en" label="English" default>
<source src="forrest_gump_no.ogg" type="audio/ogg" srclang="no" label="Norwegian">
<track src="fgsubtitles_en.vtt" kind="subtitles" srclang="en" label="English" default>
<track src="fgsubtitles_no.vtt" kind="subtitles" srclang="no" label="Norwegian">
</video>