W3C home > Mailing lists > Public > public-media-capture@w3.org > November 2016

[mediacapture-record] isTypeSupported() algorithm should be more specific

From: ddorwin via GitHub <sysbot+gh@w3.org>
Date: Mon, 21 Nov 2016 23:15:29 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-190863671-1479770126-sysbot+gh@w3.org>
ddorwin has just created a new issue for 
https://github.com/w3c/mediacapture-record:

== isTypeSupported() algorithm should be more specific ==
The [isTypeSupported() 
algorithm](https://w3c.github.io/mediacapture-record/MediaRecorder.html#dom-mediarecorder-istypesupported)
 should be more specific about checking `type`, including generally 
requiring `codecs` [1], rejecting unrecognized parameters (e.g. 
'Profiles' from RFC 6381), checking audio vs. video types, and 
determining whether multiple codecs (e.g. audio and video, if 
applicable) are supported together. The behavior for handling 
ambiguous codec strings, such as `avc1` without the avcoti, should 
also be clearly defined.

As an example, see how EME [handles MIME content type 
strings](https://w3c.github.io/encrypted-media/#get-supported-capabilities-for-audio-video-type).

[1] The codecs parameter is almost always necessary. There are few 
MIME types that specify the codec without the codecs parameter. One 
example is "audio/mpeg" for MP3.

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-record/issues/92 using your GitHub
 account
Received on Monday, 21 November 2016 23:15:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:38 UTC