Re: [blink-dev] Intent to Prototype: MediaRecorderErrorEvent API

2022-01-19 Thread Imranur Rahman 
Great, thanks. I am waiting for the spec modification.

On Wednesday, January 19, 2022 at 10:37:55 PM UTC+6 Philip Jägenstedt wrote:

> 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  
> 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  
>> wrote:
>>
>>> Contact emailsir.s...@gmail.com
>>>
>>> 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 
>>> 
>>>
>>> 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 
>>> 
>>> ?No
>>>
>>> Flag name
>>>
>>> Requires code in //chrome?False
>>>
>>> Tracking bug
>>> https://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 
>>> .
>>>
>>> -- 
>>> 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.
>>> 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
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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.
>>
> 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
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/999c970d-0746-4274-99dc-de4f71ec199an%40chromium.org.

Re: [blink-dev] Intent to Prototype: MediaRecorderErrorEvent API

2022-01-19 Thread Philip Jägenstedt 
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 
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 
> wrote:
>
>> Contact emailsir.shi...@gmail.com
>>
>> 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
>> 
>>
>> 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
>> 
>> ?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
>> .
>>
>> --
>> 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+unsubscr...@chromium.org.
>> 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
>> 
>> .
>>
> --
> 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+unsubscr...@chromium.org.
> 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
> 
> .
>

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

Re: [blink-dev] Intent to Prototype: MediaRecorderErrorEvent API

2022-01-12 Thread Domenic Denicola 
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  wrote:

> Contact emailsir.shi...@gmail.com
>
> ExplainerNone
>
> Specificationhttps://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
> 
>
> 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
> 
> ?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
> .
>
> --
> 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+unsubscr...@chromium.org.
> 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
> 
> .
>

-- 
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+unsubscr...@chromium.org.
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.

[blink-dev] Intent to Prototype: MediaRecorderErrorEvent API

2022-01-12 Thread Imranur Rahman 
Contact emailsir.shi...@gmail.com

ExplainerNone

Specificationhttps://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


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

?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
.

-- 
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+unsubscr...@chromium.org.
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.