diff --git a/MediaRecorder.bs b/MediaRecorder.bs index c837f2de..228b252a 100644 --- a/MediaRecorder.bs +++ b/MediaRecorder.bs @@ -208,8 +208,8 @@ interface MediaRecorder : EventTarget { runs the following steps:
  1. Set {{state}} to {{inactive}}.
    2. -
  2. Fire an error event named {{SecurityError}} at - target.
    3. +
  3. Fire an error event named error with a + {{SecurityError}} at target.
  4. Fire a blob event named dataavailable at target with blob.
  5. Fire an event named stop at target.
    6. @@ -222,8 +222,8 @@ interface MediaRecorder : EventTarget { following steps:
    1. Set {{state}} to {{inactive}}.
      2. -
    2. Fire an error event named {{UnknownError}} at - target.
      3. +
    3. Fire an error event named error with an + {{UnknownError}} at target.
    4. Fire a blob event named dataavailable at target with blob.
    5. Fire an event named stop at target.
      6. @@ -286,7 +286,7 @@ interface MediaRecorder : EventTarget { ✘ ✔ The minimum number of milliseconds of data - to return in a single Blob. + to return in a single {{Blob}}. @@ -302,7 +302,7 @@ interface MediaRecorder : EventTarget { task, using the DOM manipulation task source, that runs the following steps:
      1. Set {{state}} to {{inactive}} and stop gathering data.
        2. -
      2. Let blob be the Blob of collected data so far and +
      3. Let blob be the {{Blob}} of collected data so far and let target be the MediaRecorder context object, then fire a blob event named dataavailable at target with blob.
        4. @@ -369,7 +369,7 @@ interface MediaRecorder : EventTarget { (Note that blob will be empty if no data has been gathered yet.) -
      4. Create a new Blob and gather subsequent data into it.
        5. +
      5. Create a new {{Blob}} and gather subsequent data into it.
    6. return undefined.
      7. @@ -569,19 +569,30 @@ dictionary BlobEventInit { # Error handling # {#error-handling} ## General principles ## {#error-handling-principles} -This section is non-normative. - -The UA will throw a {{DOMException}} when the error can be detected at the time -that the call is made. In all other cases the UA will fire an event named -{{MediaRecorderErrorEvent}}. If recording has been started and not yet stopped -when the error occurs, let blob be the {{Blob}} of collected data so -far; after raising the error, the UA will fire a -dataavailable event with blob; immediately after the UA will then -fire an event named stop. -The UA may set platform-specific limits, such as those for the minimum and -maximum {{Blob}} size that it will support, or the number of -{{MediaStreamTrack}}s it will record at once. -It will signal a fatal error if these limits are exceeded. + +If at any moment the UA finds an error condition, the UA MUST queue a task, +using the DOM manipulation task source, that runs the following steps: +
        +
      1. Set {{state}} to {{inactive}} and stop gathering data.
        2. + +
      2. Let blob be the {{Blob}} of collected data so far and + let target be the MediaRecorder context object
        3. + +
      3. Fire a blob event named + dataavailable at target with blob.
        4. + +
      4. Fire an event named stop at target
        5. + +
      5. Fire an error event named error with an {{UnknownError}} at + target.
        6. +
      + +
      + The UA MAY set platform-specific limits, e.g. for the minimum and maximum + {{Blob}} size that it will support, or the number of {{MediaStreamTrack}}s it + will record at once. It will signal a fatal error if these limits are + exceeded. +
      ## MediaRecorderErrorEvent ## {#errorevent-section} diff --git a/MediaRecorder.html b/MediaRecorder.html index f93d3c02..fa6af742 100644 --- a/MediaRecorder.html +++ b/MediaRecorder.html @@ -1183,7 +1183,7 @@ background-attachment: fixed; } - +