Closed
Bug 753996
Opened 12 years ago
Closed 5 years ago
Functions are inconsistently unwrapped for error messages
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INVALID
People
(Reporter: sfink, Unassigned)
Details
(Whiteboard: [js:p3])
When throwing an Error whose message contains the name of a function, the JS engine calls js_ValueToFunction to produce the function name to include in the message. js_ValueToFunction does not unwrap its argument. So if the function is actually a wrapper, then js_ValueToFunction will throw a TypeError ("X is not a function"). Confusingly, this TypeError uses the decompiler, which *will* unwrap the object to get the wrapped function name out, so the final error will look something like "SomeFunction() is not a function".) Either neither or both should unwrap.
Updated•12 years ago
|
Whiteboard: [js:p3]
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Reporter | ||
Comment 1•5 years ago
|
||
We've fixed this in various ways by now.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•