-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b77
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8136317 | emb-9 | Sundararajan Athijegannathan | P3 | Resolved | Fixed | team |
| JDK-8140965 | 8u91 | Sundararajan Athijegannathan | P3 | Resolved | Fixed | b01 |
| JDK-8132970 | 8u72 | Sundararajan Athijegannathan | P3 | Closed | Fixed | b01 |
| JDK-8147334 | emb-8u91 | Sundararajan Athijegannathan | P3 | Resolved | Fixed | b01 |
var obj = { };
obj.foo();
x.js:2 TypeError: Cannot call undefined
Instead it'd be a nice debugging feature, if TypeError message looked someting like
x.js:2 TypeError: Cannot call "foo" that has undefined value
or even
x.js:2 TypeError: Cannot call "obj.foo" that has undefined value
Similar TypeError message improvement on "new" may be done as well.
obj.foo();
x.js:2 TypeError: Cannot call undefined
Instead it'd be a nice debugging feature, if TypeError message looked someting like
x.js:2 TypeError: Cannot call "foo" that has undefined value
or even
x.js:2 TypeError: Cannot call "obj.foo" that has undefined value
Similar TypeError message improvement on "new" may be done as well.
- backported by
-
JDK-8136317 TypeError messages with "call" and "new" could be improved
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-