Make DOMError constructible

Make DOMError constructible

Make DOMError constructible as per the DOM4 specification:
http://dom.spec.whatwg.org/#domerror

This matches the behavior of Firefox 28. IE11 exposes DOMError on the global
Window object but it is not constructible.

R=arv@chromium.org, tkent@chromium.org
BUG=367565
TEST=fast/dom/DOMError-constructor.html

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=172718

[tkent, 2014-04-28 01:42:24]

lgtm

[commit-bot: I haz the power, 2014-04-28 01:42:52]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ch.dumez@samsung.com/254823007/20001

[haraken, 2014-04-28 01:43:39]

LGTM

[commit-bot: I haz the power, 2014-04-28 01:48:12]

Change committed as 172718

[Inactive, 2014-04-28 02:05:22]

On 2014/04/28 01:48:12, I haz the power (commit-bot) wrote:
> Change committed as 172718

Looks like arv@ expressed some concerns on the bug. Arv@, since this has already
landed, how do you want to proceed? Do you think we should revert?

[sof, 2014-04-28 05:22:00]

On 2014/04/28 02:05:22, Chris Dumez wrote:
> On 2014/04/28 01:48:12, I haz the power (commit-bot) wrote:
> > Change committed as 172718
> 
> Looks like arv@ expressed some concerns on the bug. Arv@, since this has
already
> landed, how do you want to proceed? Do you think we should revert?

DOMError can hopefully be phased out at some point sooner; what's the motivation
for adding a constructor?

[Inactive, 2014-04-28 13:20:03]

On 2014/04/28 05:22:00, sof wrote:
> On 2014/04/28 02:05:22, Chris Dumez wrote:
> > On 2014/04/28 01:48:12, I haz the power (commit-bot) wrote:
> > > Change committed as 172718
> > 
> > Looks like arv@ expressed some concerns on the bug. Arv@, since this has
> already
> > landed, how do you want to proceed? Do you think we should revert?
> 
> DOMError can hopefully be phased out at some point sooner; what's the
motivation
> for adding a constructor?

My only motivation was to match the latest specification and Firefox's behavior.
Also note that we are currently the only browser not exposing DOMError on the
global Window object. I understand DOMError is deprecated in favor of
DOMException for new specifications. However, as far as I know, DOMError is
still used by several specifications (e.g. File API, IndexedDB, ..).

The idea of having a constructor for DOMError is so that it can be used in
polyfills
(https://github.com/whatwg/dom/commit/3f5761ef179f6784dc08c6955c5673db7552fa6e).

[arv (Not doing code reviews), 2014-04-28 13:54:11]

LGTM

Since this adds no extra code and we do use DOMError in a few places it makes
sense to fix this.