W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

DOMError -> DOMException

From: Joshua Bell <jsbell@google.com>
Date: Mon, 15 Jun 2015 09:36:43 -0700
Message-ID: <CAD649j5DNMd_eLvZbm6g4PiUkmrb0OA7uuV3DVx6PJuux4Fn5g@mail.gmail.com>
To: "public-webapps@w3.org" <public-webapps@w3.org>
Per previous discussions [1][2] highlighted in spec issues, we'd like to
remove DOMError from the platform in favor of using DOMException.

Sanity check: web-compat allowing, should we just swap DOMException in any
place DOMError is currently used?

I've done this (among other unvetted things) in the Indexed DB "v2" ED
[3][4], which exposes `error` attributes, which would now be DOMExceptions.
A Blink CL [5] passes our tests which only inspected name/message
properties. No idea yet if this is web compatible, but it seems likely
other than some test code.

Any IDL concerns about DOMException attributes? Are there expectations that
specs would have e.g. subclasses or typedefs of DOMException? I assume no
and no, but maybe others had a different vision?


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=23367
[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=21740
[3] https://github.com/w3c/IndexedDB/issues/16
[4]
https://github.com/w3c/IndexedDB/commit/42fb5845b9974b95bb0c2c446f893863ec83da2f
[5] https://codereview.chromium.org/1182233003/
Received on Monday, 15 June 2015 16:37:11 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC