- From: Mounir Lamouri <mounir@lamouri.fr>
- Date: Thu, 05 Jun 2014 23:00:50 +1000
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: Glenn Adams <glenn@skynav.com>, www-dom@w3.org
On Thu, 5 Jun 2014, at 20:57, Anne van Kesteren wrote: > On Thu, Jun 5, 2014 at 12:52 PM, Mounir Lamouri <mounir@lamouri.fr> > wrote: > > On Thu, 5 Jun 2014, at 0:27, Glenn Adams wrote: > >> According to recent tests I've performed, DOMError is implemented on > >> Firefox, but not on Chrome, Opera, or Safari. I haven't checked IE. > > > > DOMError is implemented in Chrome. Tested in current Chrome Beta (M36). > > Having a web exposed constructor to DOMError is fairly new in Blink (end > > of April). Depending on your test, you might or might not have > > considered the lack of constructor as not implemented at all. Even > > though the constructor is new, the implementation goes back to 2012 so > > Safari might likely ship DOMError too. > > The plan of action still is to get rid of DOMError in favor of > DOMException. There's no need to have both. 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. -- Mounir
Received on Thursday, 5 June 2014 13:01:16 UTC