Re: [mediacapture-record] mimeType ambiguity: "video/webm;codecs=vp8" means? (#194)

One existing model that can be considered for comparison is `addSourceBuffer()` of Media Source Extensions. If `"video/webm;codecs=vp8"` is set without `",opus"` the audio will not play the media at Chromium. Firefox will play the audio. Another compat issue. Chromium behaviour expects the parsers to be used to be explicitly set when passing codec to `addSourceBuffer()`. There does not appear to be a bright line between what users are expecting from the implementation by default and the requirement to explicitly set codecs. FWIW prefer the latter: the user explicitly sets values for the code based on well defined specification that clearly states default and non-default behaviour. 

GitHub Notification of comment by guest271314
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 18 February 2020 07:54:53 UTC