W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2013

Re: RTCError, DOMError, and... what happened?

From: Harald Alvestrand <harald@alvestrand.no>
Date: Fri, 11 Oct 2013 13:09:19 +0200
Message-ID: <5257DC5F.6040307@alvestrand.no>
To: Anne van Kesteren <annevk@annevk.nl>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 10/11/2013 10:24 AM, Anne van Kesteren wrote:
> On Fri, Oct 11, 2013 at 6:58 AM, Harald Alvestrand <harald@alvestrand.no> wrote:
>> On 10/10/2013 11:35 PM, Travis Leithead wrote:
>>> Just to throw out a note of caution, I believe that Anne now intends to deprecate/remove DOMError altogether, and just use DOMException objects directly. The goal as I infer it, is to unify all exception/error processing in the DOM into the one object for simplicity and uniformity. (The multitude of *Error objects is ECMAScript is not seen as a great design.)
>> Calling Anne - can you comment?
> I told you this:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22251#c7 Unfortunately
> the story is still not clear. It's kinda tricky to find the right way
> forward here. Sorry.
Thanks for the update!

Just to verify:

- All paths forward will use error objects that contain "name" and 
"message" fields, right?
- The "name" field will still have defined values that are in 
camelCaseWithInitialLowerCase, right?

I think that's the parts people were first of all hoping to see no 
change to.
Received on Friday, 11 October 2013 11:09:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:51 UTC