Be more resilient when IE DOMParser fails
Fixes JSTOR in IE
This commit is contained in:
parent
0e2cf3146f
commit
cd6d528519
|
@ -970,6 +970,10 @@ Zotero.Utilities = {
|
||||||
var rootDoc = element.ownerDocument;
|
var rootDoc = element.ownerDocument;
|
||||||
} else if(element.documentElement) {
|
} else if(element.documentElement) {
|
||||||
var rootDoc = element;
|
var rootDoc = element;
|
||||||
|
} else if(Zotero.isIE && element.documentElement === null) {
|
||||||
|
// IE: documentElement may be null if there is a parse error. In this
|
||||||
|
// case, we don't match anything to mimic what would happen with DOMParser
|
||||||
|
continue;
|
||||||
} else {
|
} else {
|
||||||
throw new Error("First argument must be either element(s) or document(s) in Zotero.Utilities.xpath(elements, '"+xpath+"')");
|
throw new Error("First argument must be either element(s) or document(s) in Zotero.Utilities.xpath(elements, '"+xpath+"')");
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue
Block a user