Open
Bug 1292172
Opened 8 years ago
Updated 10 months ago
new Proxy(new Error, ...) never contains stacktrace
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: michalwadas, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: triage-deferred)
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160604131506
Steps to reproduce:
try {
throw new Error;
} catch(e) {
console.log(e.stack)
}
try {
throw new Proxy(new Error, {});
} catch(e) {
console.log(e.stack)
}
Related Chrome issue: https://bugs.chromium.org/p/chromium/issues/detail?id=634340
Actual results:
"@debugger eval code:2:10"
""
Expected results:
"@debugger eval code:2:10"
""@debugger eval code:7:10"
|
||
Updated•7 years ago
|
Keywords: triage-deferred
Priority: -- → P3
|
Reporter | |
Comment 1•3 years ago
|
||
Still happens on Firefox 94.
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Comment 2•10 months ago
|
||
Still broken in Chrome too; needs some investigation to see if this is actually working as expected (by spec let's say) or not.
Blocks: sm-runtime
You need to log in
before you can comment on or make changes to this bug.
Description
•