W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2009

[whatwg] HTML5 video element - default to fallback in cases where UA can't play format

From: Kit Grose <kit@iqmultimedia.com.au>
Date: Wed, 28 Oct 2009 14:15:37 +1100
Message-ID: <99B7AA91-7A23-438E-8FA4-9C36C2D50279@iqmultimedia.com.au>
Thanks for the really in-depth reply; you make some excellent points  
(particularly defining a video source file with the src attribute). I  
think it all boils down to the fact that canPlayType() can return  
"maybe"; and in those cases the expected behaviour I mention isn't  
easily definable.

In our particular case, relying on Javascript isn't a deal-breaker so  
we'll go forward that way until we can see some commercial benefit  
targeting Gecko users more actively.

I do think this will mean holding out on one of the most exciting new  
features of HTML5 for the foreseeable future for client work, though  
(at least until we see what the MSIE roadmap for support looks like;  
if they require yet another new format, we'll inevitably change from a  
<video>/QT/Flash hierarchy to just QT/Flash (and lose practically  
nothing). Yet again, I think the defining factor will be the mobile  
web; if hardware decoders for OGG become cheap enough to be reasonably  
added to iPhones and Blackberries, etc. the incentive to quickly  
migrate away from Flash is more clear.

Thanks for your detailed response!

?Kit
Received on Tuesday, 27 October 2009 20:15:37 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:18 UTC