Summary: | Mechanism for storing line numbers and source URLs in JavaScript exceptions needs improvement | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> | ||||
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | ap, burg, ggaren, joepeck, levin, oliver, pmuellr, rik, zwarich | ||||
Priority: | P2 | Keywords: | HasReduction, InRadar | ||||
Version: | 523.x (Safari 3) | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
David Kilzer (:ddkilzer)
2008-05-02 14:42:28 PDT
Created attachment 20932 [details]
Test cases
Additional fun facts:
- Throwing an exception inside a function body from an onclick handler results in "undefined" for the description--always.
- Throwing an object with just a "sourceURL" line will cause that URL to be printed in the Web Inspector.
It would be good to provide a set of tests to run across browsers to capture what everyone is doing here. Basically, something like Dave's tests that just run and produce results. But also include some of the existing 'built-in' exceptions, both thrown by existing internal code, as well as cons'd up by the user (eg, someone write's code that does a "throw new Error()") *** Bug 62897 has been marked as a duplicate of this bug. *** The regular object and the primitive cases should work now. I think we are still deliberately deferring to properties on objects if there's a lineNo property |