Bug 55347 – "name" and "message" enumerable on *Error.prototype

• Component: JavaScriptCore
• Status: RESOLVED FIXED

[Mark S. Miller]

See https://bugzilla.mozilla.org/show_bug.cgi?id=637207 and
http://code.google.com/p/v8/issues/detail?id=1215

For all so-called NativeError.prototype objects, their "name" and "message"
properties are enumerable when they shouldn't be. Error itself has this problem for 'message' but not for 'name'.

The "message" property's value should be the empty string. But on all the NativeError.prototype objects its value is instead the same as "name" -- the name of the corresponding constructor.

I am classifying this as minor since an initialization script can easily repair
this using Object.defineProperty.

[Gavin Barraclough]

Fixed in r88559

[Mark S. Miller]

> Fixed in r88559

Not quite. In r93580 I get

RangeError.prototype 15.11.7.7 .message doesn't have expected value: should be "" but was "RangeError"
TypeError.prototype 15.11.7.7 .message doesn't have expected value: should be "" but was "TypeError"
EvalError.prototype 15.11.7.7 .message doesn't have expected value: should be "" but was "EvalError"
URIError.prototype 15.11.7.7 .message doesn't have expected value: should be "" but was "URIError"
ReferenceError.prototype 15.11.7.7 .message doesn't have expected value: should be "" but was "ReferenceError"
SyntaxError.prototype 15.11.7.7 .message doesn't have expected value: should be "" but was "SyntaxError"

(From http://erights.org/tests/testjs/ )

[Gavin Barraclough]

Ooops, scanned this bug too quickly, yep, incomplete job. Reopening.

Thanks for catching this Mark.

[Gavin Barraclough]

Created attachment 104889 [details]
Fix value of message.

[Gavin Barraclough]

Okay, hopefully really should be fixed in r93624!