Need to rewire Error inheritance to keep UnsafeError hidden

[GoogleCodeExporter]

For each of the builtin "subclasses" of Error, such as EvalError, ES6 changes 
them the constructors themselves to inherit directly from the Error 
constructor, in order to be analogous to ES6's handling of user defined 
classes. Chrome 44 Canary now implements this.

However, debug.js hides the original Error constructor for its own use as 
UnsafeError, replacing it with FakeError. However, it still would have been 
accessible via, for example, Object.getPrototypeOf(EvalError) or 
EvalError.__proto__. Fortunately, the new error checking we added to startSES 
caught this, so no unsafety results. Unfortunately, this results in SES (and 
therefore Caja in ES5 mode) reporting that it cannot initialize safely on 
Chrome 44 Canary.

Original issue reported on code.google.com by erights on 12 Apr 2015 at 12:33

[GoogleCodeExporter]

Original comment by erights on 12 Apr 2015 at 12:55

• Changed title: Need to rewire Error inheritance to keep UnsafeError hidden

[GoogleCodeExporter]

Original comment by erights on 21 Jun 2015 at 10:33

• Changed state: Fixed

[GoogleCodeExporter]

Nevermind. Followed wrong link. The issue itself is really at 
https://github.com/google/caja/issues/1961 and already closed.

Original comment by erights on 21 Jun 2015 at 10:36