Re: [blink-dev] MediaRecorder: heads up changing mimeType style

[Harald Alvestrand]

I don't think the double quotes are required, actually.

http://tools.ietf.org/html/rfc7231#section-3.1.1.1 (the HTTP spec) says that a parameter must be a "token" or a quoted-string; most of the time, I see people use tokens when they have no need to encode weird stuff like spaces or punctuation inside the parameter.

Unless someone can find a spec that says they're required, I think we should be liberal in what we accept; my personal preference is to send the "token" form too.

On Fri, Dec 18, 2015 at 11:20 PM, David Dorwin <ddo...@chromium.org> wrote:

Thank you for addressing this.

Note that the strings below are missing double quotes around the codec names. They should be:

'video/webm', 'video/webm;codecs="vp8"', 'video/webm;codecs="vp9"', 'audio/webm;codecs="opus"' 

On Fri, Dec 18, 2015 at 2:12 PM, Miguel Casas-Sanchez <mca...@chromium.org> wrote:

This only pertains to MediaRecorder [1] constructor dictionary and isTypeSupported() method.

Currently the expected/supported MIME types are in the form of 'video/vp8', 'audio/opus' etc, the CL [2] changes that to the more conforming MIME e.g. 'video/webm', 'video/webm;codecs=vp8', 'video/webm;codecs=vp9', 'audio/webm;codecs=opus' following webm container guidelines [3].

Happy recording! 

[1] http://w3c.github.io/mediacapture-record/MediaRecorder.html 

[2] https://crrev.com/1534553003

[3] http://www.webmproject.org/docs/container/, Section "HTML5 Video Type Parameters"

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Miguel Casas-Sanchez]