[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 #54 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Adrian: We shouldn't have any bugs. I think we're agreed on this. Just like
decoding should be reliable everywhere, recognising the stream should be
reliable everywhere.

I'm not sure why you consider it a layering violation. It's exactly correctly
layered: the network layer would be marking the stream as being the type that
the specs say it should be treated as. This seems quite appropriate.

However, if what you're saying is that you won't change, then let's turn to
foolip. Is there any change Blink could get fixed to follow the Content-Type
header and not sniff?

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

Received on Wednesday, 15 January 2014 22:26:08 UTC