[Bug 11984] <video>: Figure out the story with respect to honouring Content-Type headers vs sniffing content

https://www.w3.org/Bugs/Public/show_bug.cgi?id=11984

--- Comment #52 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to Ian 'Hixie' Hickson from comment #51)
> What you call a "quality of implementation" issue is what I would call an
> "interoperability" issue. :-) The consequences are that something that works
> ok in one browser doesn't work ok in another.

Except that you're only talking about being interoperably broken. There are
plenty of ways in which a browser might have a bug where it can't play content
that is playable elsewhere. There's little value in sharing bugs in content
recognition but not in content playback (actually there's little value in
sharing bugs - we should each just fix them according to our prioritization
strategies).

> Do you have access to the stream at all? For example, can you read the first
> few bytes, compare it to a table, override the Content-Type accordingly, and
> then pass it to the media system asking it to be strict?

No, we don't handle the stream. The request is made from the media engine. It
goes through the browser network stack but it would be a layering violation to
add the sniffing there.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 14 January 2014 19:16:58 UTC