Re: DOMError Status
Glenn Adams <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <CACQ=j+d8yQSULAHWbF9EePedy6fTxqWeE8OmLBnKUkDgw7nv-A@mail.gmail.com> |
On Thu, Jun 5, 2014 at 4:57 AM, Anne van Kesteren <[email protected]> wrote: > On Thu, Jun 5, 2014 at 12:52 PM, Mounir Lamouri <[email protected]> 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. > Agree. However, as long as DOMError is defined in dom4, it is a normative feature that needs to be implemented, and will be tested by compliance testing regimes. In any case, it is relevant when proposing transition to PR if there are two implementations of every defined feature. > > > -- > http://annevankesteren.nl/ >