Addresses #1829: [PATCH] wpdDOMSaver fails due to undefined Zotero

Removes calls to Zotero object, since they are unnecessary (the call that was problematic was a workaround for a Fx 4 beta crashing bug).
This commit is contained in:
Simon Kornblith 2011-06-17 21:25:05 +00:00
parent 9b62937361
commit fc078caddf

View file

@ -296,14 +296,12 @@ var wpdDOMSaver = {
aNode.StopPlay();
dump ("ready! \n");
} catch (e) {} */
if(!Zotero.isFx4) {
try {
var container = aNode.QueryInterface(Components.interfaces.nsIImageLoadingContent)
.getRequest(Components.interfaces.nsIImageLoadingContent.CURRENT_REQUEST)
.image;
container.animationMode = Components.interfaces.imgIContainer.kDontAnimMode;
} catch(e) {}
}
try {
var container = aNode.QueryInterface(Components.interfaces.nsIImageLoadingContent)
.getRequest(Components.interfaces.nsIImageLoadingContent.CURRENT_REQUEST)
.image;
container.animationMode = Components.interfaces.imgIContainer.kDontAnimMode;
} catch(e) {}
},
// get the node value of aNode directly from the actual DOM tree (WPD_CLONENODEBUG)
@ -654,7 +652,7 @@ var wpdDOMSaver = {
catch (e) {
var msg = "Unable to access cssRules property of " + aCSS.href
+ " in wpdDOMSaver.processCSSRecursively()";
Zotero.debug(msg, 2);
dump("WebPageDump: "+msg+"\n\n", 2);
Components.utils.reportError(msg);
return "";
}