Conflict with DOMException

[annevk]

I don't like this as DOMException has Error in its prototype chain so we'd end up shadowing this new property making it useless in a lot of web platform code.

The web platform has established a pattern whereby if the name field is not granular enough you create a subclass of DOMException for the domain in question with specific fields that make sense.

[jasnell]

It would only shadow in cases like DOMException where code has an established meaning. We're not changing DOMException here so this really wouldn't be web breaking. I'm not convinced this is a strong enough reason against this and I'm not convinced that we should be letting DOMException constrain language-level changes.

[annevk]

Why would it only shadow in those cases? code is always present.

And even then, in the vast majority of cases code returns a non-0 value.

[jasnell]

Code is always present on DOMException. But like cause, it's only installed as an own property on Error if it is passed as an option on construction, and DOMException does not pass it to the super(...).