Good catch, thanks Domenic!

Dom put up https://github.com/w3c/mediacapture-record/pull/212 to change
the spec here.

Imranur, once the spec change is made, I would suggest sending an Intent to
Ship. An Intent to Prototype is for when you want to implement something
behind a flag, but not ship it yet.

Best regards,
Philip

On Wed, Jan 12, 2022 at 6:06 PM Domenic Denicola <[email protected]>
wrote:

> This seems like a problematic specification. They should just use
> ErrorEvent, instead of creating a new class that is basically identical. I
> have filed https://github.com/w3c/mediacapture-record/issues/211 and hope
> we can go that route instead.
>
> On Wed, Jan 12, 2022 at 11:59 AM Imranur Rahman <[email protected]>
> wrote:
>
>> Contact [email protected]
>>
>> ExplainerNone
>>
>> Specification
>> https://w3c.github.io/mediacapture-record/#errorevent-section
>>
>> Summary
>>
>> MediaRecorderErrorEvent is fired when Media Recording API faces an error.
>> This API will enable developers to debug more conveniently when an
>> exception occurs in Media Recording API. MediaRecorderErrorEvent will
>> provide further details about the error with a DOMException object. BUG:
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1250432 SPEC:
>> https://w3c.github.io/mediacapture-record/#errorevent-section
>>
>>
>> Blink componentBlink>MediaRecording
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMediaRecording>
>>
>> Motivation
>>
>> The main motivation is that currently Chromium fires a plain event,
>> whereas if this feature is implemented the developers will have more
>> knowledge about the occurred error in Media Recording API and debug
>> conveniently.
>>
>>
>> Initial public proposal
>>
>> TAG review
>>
>> TAG review statusNot applicable
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>>
>>
>> Gecko: No signal
>>
>> WebKit: No signal
>>
>> Web developers: No signals
>>
>> Other signals:
>>
>>
>> Debuggability
>>
>>
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>> ?No
>>
>> Flag name
>>
>> Requires code in //chrome?False
>>
>> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1250432
>>
>> Estimated milestones
>>
>> No milestones specified
>>
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5103987136135168
>>
>> This intent message was generated by Chrome Platform Status
>> <https://chromestatus.com/>.
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEq642EJPBbCQUGJ%2BuQAFrEi1HXZZAA%3D81x6-ZjdPYZ%3DJcWWqA%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEq642EJPBbCQUGJ%2BuQAFrEi1HXZZAA%3D81x6-ZjdPYZ%3DJcWWqA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8OS3ffZcfONb-nEz0y3diWWaC3Xo%3Dh8W2ORK_hxQ6fEg%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra8OS3ffZcfONb-nEz0y3diWWaC3Xo%3Dh8W2ORK_hxQ6fEg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYdkQYci8A%3DqqyGirhGZ17zckVKo7yaQApHFUbE7reC5Mw%40mail.gmail.com.

Reply via email to