This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21702 - Make the usage of content sniffing for decodeAudioData explicit
Summary: Make the usage of content sniffing for decodeAudioData explicit
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-15 21:46 UTC by Ehsan Akhgari [:ehsan]
Modified: 2014-10-28 17:18 UTC (History)
1 user (show)

See Also:

Attachments

Description Ehsan Akhgari [:ehsan] 2013-04-15 21:46:34 UTC 
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.
Comment 1 Olivier Thereaux 2014-10-28 17:15:05 UTC 
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 2 Olivier Thereaux 2014-10-28 17:18:05 UTC 
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.