| Summary: | DOMException thrown for JSON.stringify XMLHttpRequest in Chrome 21+ | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Simon Kaegi <simon_kaegi> |
| Component: | Client | Assignee: | Simon Kaegi <simon_kaegi> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne, ken_walker, mamacdon, pwebster |
| Version: | 0.5 | Flags: | ken_walker:
review+
|
| Target Milestone: | 0.5 RC3 | ||
| Hardware: | PC | ||
| OS: | Windows Server 2008 | ||
| Whiteboard: | |||
|
Description
Simon Kaegi
I'm hopeful we will get a quick response from the Chrome team however...
A vaguely unsettling fix to cover the immediate problem for this might be to put something like..
if (error && error.xhr) {
delete error.xhr;
}
in the two spots in plugin.js (~line 100 and 110) to ensure an xhr is not stringified.
Looks good - running a build with this change For 0.5 we're using the following JSON stringify replacer to specifically target the XHR case...
function jsonXMLHttpRequestReplacer(name, value) {
if (value && value instanceof XMLHttpRequest) {
return {
status: value.status,
statusText: value.statusText
};
}
return value;
}
Will come back and close after we've done further verification.
Can this be marked fixed now? I also noticed the bug has been fixed upstream in Chrome already. . |