Bug 35140
| Summary: | Wrong string return for DOM XSLTProcessor and XMLDocument toString() call | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Marc Bonnier <chrome> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Trivial | CC: | ap |
| Priority: | P3 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Marc Bonnier
I know this does not break anything but just for the sake of consistency ...
1) The window.XSLTProcessor.toString() call returns:
"[object XSLTProcessorConsructor]" instead of:
"[object XSLTProcessorConstructor]" (little typo :).
2) The window.XMLDocument.toString() call returns:
"[object DocumentConstructor]" instead of:
"[object XMLDocumentConstructor]" (all the others consistent with the window property name).
Thanks.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
(2) happens because XMLDocument is just an alias for Document we have for compatibility. There is no such thing as XMLDocument in HTML5 or WebKit. So, this is expected behavior.
(1) is something to be fixed, of course.
Alexey Proskuryakov
(1) has been fixed in <http://trac.webkit.org/changeset/61136>.