| Summary: | [V8] DOMCoreException should be visible as DOMException | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Jian Li <jianli> | ||||
| Component: | WebCore Misc. | Assignee: | Jian Li <jianli> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | dglazkov | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
Created attachment 49763 [details]
Proposed Patch
Comment on attachment 49763 [details]
Proposed Patch
Yay for passing layout tests!
Committed as http://trac.webkit.org/changeset/55416. |
We need to make DOMCoreException be visible as DOMException, similar to what JSC code generator does. This will fix several wrong layout test results, like LayoutTests/fast/dom/DOMException/prototype-object.html has the following wrong result: FAIL Object.prototype.toString.call(e) should be [object DOMException]. Was [object DOMCoreException]. ... FAIL e.constructor.toString() should be [object DOMExceptionConstructor]. Was function DOMCoreException() { [native code] }. This will also apply to FormData interface I am going to add at 26979.