- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 11 Feb 2014 17:11:26 +0000
- To: Matt Brubeck <mbrubeck@mozilla.com>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
On Tue, Feb 11, 2014 at 4:54 PM, Matt Brubeck <mbrubeck@mozilla.com> wrote: > On 2/3/2014 6:05 AM, Anne van Kesteren wrote: >> Over in DOM/IDL land we are still unsure around DOMException and >> especially new names for it. > > Could you give us a pointer to the latest documentation or discussion on > this? Is there any consensus emerging around an alternative? There's http://esdiscuss.org/topic/error-objects-in-w3c-apis and there's a couple of bugs filed on IDL to import everything from DOM regarding errors. >> Given that the semantics of your exception perfectly match JavaScript's >> built-in RangeError exception I strongly recommend using that over minting >> something new. > > We're open to changing this, though we might want to double-check that there > isn't too much existing content depending on the shipping implementation in > IE11. (We expect there is not.) > > However, we're not sure that RangeError is really a perfect match. Active > pointerIds do not necessarily form a contiguous range. For example, 5 and 7 > might be valid arguments to setPointerCapture, while 6 is invalid. It seems > surprising for setPointerCapture(6) to throw a RangeError in that case. Is > there any other existing DOM or ECMAScript error that is a better fit? RangeError would still be correct in that case I think. See http://people.mozilla.org/~jorendorff/es6-draft.html#sec-string.prototype.normalize for precedent. -- http://annevankesteren.nl/
Received on Tuesday, 11 February 2014 17:11:54 UTC