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

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

From: David Singer <singer@apple.com>
Date: Thu, 20 May 2010 09:44:12 -0700
Message-ID: <02249910-B9DE-4021-A69C-E5F87998A5FC@apple.com>
Did anyone revise the registration of application/octet-stream to add parameters?

On May 20, 2010, at 3:36 , Simon Pieters wrote:

> On Thu, 20 May 2010 11:55:01 +0200, Robert O'Callahan <robert at ocallahan.org> wrote:
> 
>> 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 bug report was about application/octet-stream *with parameters*, e.g. application/octet-stream; codecs="theora, vorbis". The spec had the requirement about application/octet-stream before that bug report.
> 
> 
>> 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
> 
> 
> -- 
> Simon Pieters
> Opera Software

David Singer
Multimedia and Software Standards, Apple Inc.
Received on Thursday, 20 May 2010 09:44:12 UTC

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