Re: [mediacapture-record] Clarification needed for mime type handling (#170)

> ctor-mime is the recorder's mimeType attribute just after running the MediaRecorder constructor

Right, the name threw me, but the legend helps (it is *not* the value passed into the constructor).

My 2 cents:

1. Modify the type? I'd say no. It should throw if it can't handle the input. But if parameters are absent, then see 2.
2. From "all parameters", I'd say yes, modulo "final" (see 3). E.g. pass in `"audio/webm"`, read `"audio/webm;codecs=opus"`. But neither of the browsers do this. Seems useful though.
3. `read-only` to me doesn't mean a value is constant, only that it has no setter. So in the case where no value was passed in by the app, I don't see a contradiction. if something is passed in however, I agree it seems unclear what to do. See 4.
4. I'm happy to cement existing implementation behavior here. We've taken that approach before in this spec, and it seems reasonable here as well.

If this needs clarification, I'm happy to review a PR.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/170#issuecomment-503312516 using your GitHub account

Received on Tuesday, 18 June 2019 21:08:04 UTC