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

Re: Encoding API exceptions

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 10 Nov 2014 19:33:47 +0100
Message-ID: <CADnb78hFMU9g=N0pzG5SEVJ14oZDxo_o8=VNEg6ruAqxeJJB_Q@mail.gmail.com>
To: Joshua Bell <jsbell@google.com>
Cc: "www-international@w3.org" <www-international@w3.org>, Masatoshi Kimura <VYV03354@nifty.ne.jp>, Boris Zbarsky <bzbarsky@mit.edu>, Domenic Denicola <d@domenic.me>, Allen Wirfs-Brock <allenwb@mozilla.com>
On Mon, Nov 10, 2014 at 6:41 PM, Joshua Bell <jsbell@google.com> wrote:
> It'd be nice to have more confidence about starting to use RangeError in web
> platform features; IIRC an early iteration of the Encoding API design did
> use RangeError but we moved away from it! Is there a new spec/feature that
> can test the waters first?

Anything that uses enum could be used. Since TextDecoder/TextEncoder
are not really using enum, it seemed like an easy enough place to
start. https://fetch.spec.whatwg.org/ also uses RangeError for
statuses that have to be within a range.

Received on Monday, 10 November 2014 18:34:17 UTC

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