- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Mon, 10 Nov 2014 19:33:47 +0100
- 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. -- https://annevankesteren.nl/
Received on Monday, 10 November 2014 18:34:17 UTC