W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2010

[whatwg] Video with MIME type application/octet-stream

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 20 May 2010 21:55:01 +1200
Message-ID: <AANLkTim7DBumwPZi6GOQrGJqXBE_peupNPYmnrAhKr1I@mail.gmail.com>
I just became aware that application/octet-stream is excluded from being a
type "the user agent knows it cannot render".
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#a-type-that-the-user-agent-knows-it-cannot-render
Apparently this was done in response to a bug report:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7977
Neither the bug report nor the editor's response give any indication why
this change was made.

This change means files served with application/octet-stream will make it
all the way to the step "If the media
data<http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#media-data>can
be fetched but is found by inspection to be in an unsupported format
...", so implementations have to add support for binary sniffing for all the
types they support. We didn't need this before in Gecko. What was the
motivation for adding this implementation requirement?

Thanks,
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/20100520/397788db/attachment.htm>
Received on Thursday, 20 May 2010 02:55:01 UTC

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