- From: Mounir Lamouri <mounir@lamouri.fr>
- Date: Sat, 07 Jun 2014 23:23:43 +1000
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Glenn Adams <glenn@skynav.com>, www-dom@w3.org
On Sat, 7 Jun 2014, at 7:14, Anne van Kesteren wrote: > On Thu, Jun 5, 2014 at 3:00 PM, Mounir Lamouri <mounir@lamouri.fr> wrote: > > Sure. That sounds pretty orthogonal to whether DOMError is implemented > > or not. DOMError is required by IndexedDB which is implemented by > > Firefox, Chrome, Opera, IE and now Safari so unless IDB has a path > > forward to deprecate DOMError, it is likely going to leave along side > > DOMException. > > Why could usage in Indexed DB not be replaced by DOMException? So, I said "unless IDB has a path forward to deprecate DOMError", I didn't say that it will not happen ;) But, this said, I'm not sure it would be easy given that DOMError and DOMException do not match. The former exposes "name" and "message" while the second exposes "code". If any content out there uses the returned DOMError, the deprecation path will not be as easy as switching to DOMException. Though, if IDB is the only API really using DOMError, the deprecation path could be to have DOMError replaced by IDBError in the IDB specification and define IDBError in a way that will not break current content. -- Mounir
Received on Saturday, 7 June 2014 13:24:08 UTC