- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Mon, 13 Jul 2009 10:00:20 +1200
On Sun, Jul 12, 2009 at 10:34 AM, Philip J?genstedt <philipj at opera.com>wrote: > Not that I except this discussion to go anywhere, but out of curiosity I > checked how Firefox/Safari/Chrome actually implement canPlayType: > > http://wiki.whatwg.org/wiki/Video_type_parameters#Browser_Support > > Firefox is conservative and honest (except maybe for "audio/wav; codecs=0", > what could you do with the RIFF DATA chunk?) Wave codec 0 means "unknown codec", so we return "maybe", but we should actually return "no" since in practice we refuse to play a file with 0 in the format field. We'll fix that. Safari gets maybe/probably backwards compared to what the spec suggests. > Chrome seems to ignore the codecs parameter, claiming "probably" even for > bogus codecs. Authors obviously can't trust the distinction between "maybe" > and "probably" to any extent. > Please file bugs against those browsers --- especially Chrome, since they haven't shipped video support yet. It's not hard to implement this right, these issues reflect sloppy development more than a fundamental problem IMHO. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090713/6b0e5d87/attachment.htm>
Received on Sunday, 12 July 2009 15:00:20 UTC