W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] Make the usage of content sniffing for decodeAudioData explicit (#57)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:27:59 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/57@github.com>
> Originally reported on W3C Bugzilla [ISSUE-21702](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21702) Mon, 15 Apr 2013 21:46:34 GMT
> Reported by Ehsan Akhgari [:ehsan]
> Assigned to 

We should probably explicitly say in the spec that the buffer passed to decodeAudioData should be sniffed to get the content type, according to the http://mimesniff.spec.whatwg.org/ spec, and that the implementation must reject buffers that do not pass that content sniffing.

This will help in situations like https://bugzilla.mozilla.org/show_bug.cgi?id=861187, where one implementation (Gecko) cannot sniff the content type properly but another (WebKit) can.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/57
Received on Wednesday, 11 September 2013 14:29:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC