W3C home > Mailing lists > Public > www-international@w3.org > October to December 2014

Re: Encoding API exceptions

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Thu, 13 Nov 2014 22:39:49 -0500
Message-ID: <54657985.5090103@mit.edu>
To: Anne van Kesteren <annevk@annevk.nl>, "www-international@w3.org" <www-international@w3.org>
CC: Joshua Bell <jsbell@google.com>, Masatoshi Kimura <VYV03354@nifty.ne.jp>, Domenic Denicola <d@domenic.me>, Allen Wirfs-Brock <allenwb@mozilla.com>
On 11/9/14, 4:45 AM, Anne van Kesteren wrote:
> Both Chromium and Gecko implement the API. There's interest in this
> API from the wider JavaScript community.

I expect that a bigger issue than the exact type of exception that's 
thrown will be things like whether the attributes are accessors or value 
props, whether they're actually readonly, what arguments are allowed 
(e.g. the USVString bit for TextEncoder),

> Unfortunately for them we use a DOMException which so far is the only dependency on "DOM things".

Well, apart from the Web IDL dependency, no?

> I was wondering if there would be interest in changing both Chromium
> and Gecko to throw TypeError where we now throw EncodingError, and
> throw RangeError where we now throw TypeError.

I think this would be fine in compat terms; I doubt anyone is depending 
on the current exception types here.

Received on Friday, 14 November 2014 03:40:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC