Hey, you started this. And I'm sorry if my brilliance bores you.![]()
This is the joy of multiple source tags:it puts me to sleep too, and as much as the (mac) flash plugin was an adobe abomination at least until Jobs kicked them in the nads over it, when I do embeded video I now have to dance around who what where supports what in the alternative content.
<video width="320" height="240" controls="controls">
<source src="movie.mp4" type="video/mp4" />
<source src="movie.ogg" type="video/ogg" />
Your browser does not support the video tag.
</video>
This is the joy of multiple source tags:You get all browsers that way.Code:<video width="320" height="240" controls="controls"> <source src="movie.mp4" type="video/mp4" /> <source src="movie.ogg" type="video/ogg" /> Your browser does not support the video tag. </video>
Take a look here for more info.
Snazzy. I didn't realize the browser would be responsible for determining which video to play. I haven't had a chance to play much with HTML5 yetThis is the joy of multiple source tags:You get all browsers that way.Code:<video width="320" height="240" controls="controls"> <source src="movie.mp4" type="video/mp4" /> <source src="movie.ogg" type="video/ogg" /> Your browser does not support the video tag. </video>
Take a look here for more info.
Yeah, it's great to create a page where you don't have to worry about what browser the user is using.Snazzy. I didn't realize the browser would be responsible for determining which video to play. I haven't had a chance to play much with HTML5 yet
The problem, still, with video is that this will only allow for progressive downloads of the videos. So you can only play what has downloaded so far. In order for you to jump around to parts that haven't yet loaded, like YouTube does, there would be some kind of server-side requirement.
The only way it could is if the specifications mandated that the browsers tell the server to "resume" downloading the video from the specified point, and even in this case (which seems unlikely to me), the web server would have to support resuming downloads (not all do). Which still means that there would be some server-side requirement. HTML5 is, after all, just a markup language and not an API.As for the progress bit, I'm fairly confident that if you click ahead, it will play from there. Granted, it's not as smooth as YouTube but it works.
I agree.I think the best way to see if this is the case it to test it. I might have to try that later.