Yes, warnings are in the spec, but they are controversial and may be removed. I've been leaving them in the draft as a reminder that they may be needed, since I figure that's better for implementers than sticking them in at the last moment. However we haven't been doing any work on them. - Jim From: Rachel Blum [mailto:groby@google.com] Sent: Tuesday, September 03, 2013 4:43 PM To: Jim Barnett Cc: Greg Billock; Mandyam, Giridhar; Robert O'Callahan; public-media-capture@w3.org Subject: Re: [Marketing Mail] Re: MediaStream Recording : record() method On Tue, Sep 3, 2013 at 12:02 PM, Jim Barnett <Jim.Barnett@genesyslab.com<mailto:Jim.Barnett@genesyslab.com>> wrote: Question: if we decide to add the concept of 'warnings' (as opposed to errors), should the UA raise a warning if the app specifies a value outside the platform-specific limits? We already do have the concept of warnings. Section 5.1: "If a non-fatal error occurs during recording, the UA SHOULD raise a recordingwarning event, with data indicating the nature of the problem, and continue recording." At this point, it is then up to the UA to treat platform constraint violations as either fatal or a warning. (I'm reluctant to do that in the spec, since it might well depend on the implementation) - rachel
Received on Tuesday, 3 September 2013 20:46:49 UTC