> Like you, I think that <video> element is a good thing, easier to > manipulate than <object> element. Nowadays, there are more and more > videos on the Web and we shouldn't let Flash inaccessible and > in-interoperable video players playing all multimedia video content. So, > we have to use a simple useful element to insert easily a video on a > webpage. <video> element could do that. I don't think this has anything to do with Flash nor should it. Apples and oranges. I also think <video> is a great idea, however I would like to see the ability to change the playback speed of the movie through the API (eg. x0.5, x1.5, x2, etc). I think there is a strong use case for usability in being able to change the playback rate. I often watch recorded talks/lectures (like the talk Timb recently gave about the future of the Web to US Congress [1]) in Windows Media Player at x2 the normal playback rate. I think such functionality would be helpful to a lot of people, particularly in an educational setting. And I also think it's about time that <audio> becomes a first class citizen too!:) Kind regards, -- Marcos Caceres http://datadriven.com.au [1] http://www.w3.org/News/2007#item35Received on Saturday, 17 March 2007 01:51:56 UTC
This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:21:34 UTC