RE: [DOMError]: Subclassing DOMError to increase granularity of error handling?
"Nilsson, Claes1" <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <6DFA1B20D858A14488A66D6EEDF26AA301A33878B423@seldmbx03.corpusers.net> |
Ok, thanks for this information Anne. I guess that I should keep the current solution in the Raw Socket API until the DOMException solution has been defined in the DOM specification. BR Claes > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Anne van Kesteren > Sent: den 6 augusti 2013 11:54 > To: Nilsson, Claes1 > Cc: [email protected]; [email protected] > Subject: Re: [DOMError]: Subclassing DOMError to increase granularity > of error handling? > > On Tue, Aug 6, 2013 at 10:24 AM, Nilsson, Claes1 > <[email protected]> wrote: > > WDYT about this approach? Is this a reasonable solution? > > DOMError is going away. We only need DOMException. Allen (editor of > ECMAScript) did suggest we do something like what you suggest. Have > DOMException.prototype.subname which gives a more detailed name and > ideally have DOMException.name be "DOMException" but we can probably no > longer do that. Still need to work out the details here unfortunately > as apparently last time we thought we figured error handling out we > didn't :/ > > > -- > http://annevankesteren.nl/