Re: [Xsltforms-support] "n is undefined" in rev 497 and 498
Brought to you by:
alain-couthures
From: Grégoire C. <gco...@gm...> - 2011-04-11 09:17:42
|
Le 11/04/2011 11:00, Grégoire COLBERT a écrit : > Hi! > > With revisions 498 and 497, I get "n is undefined" after a submission to > my server (it's ok with 496). The problem is in the > "NodeTestAny.evaluate" function. I fixed it using : > > NodeTestAny.prototype.evaluate = function(node) { > var n = node.localName || node.baseName; > // return n.substr(0, 10) != "xsltforms_" && node.namespaceURI != > "http://www.w3.org/2000/xmlns/"; > return (n !== undefined) ? (n.substr(0, 10) != "xsltforms_" && > node.namespaceURI != "http://www.w3.org/2000/xmlns/") : false; > }; > > Though the fix is obvious, I wonder if this is theorically possible that > an undefined node reach this function? Since I don't know what you're > trying to do with namespaces, I don't know if this is a test that was > forgotten or something deeper. > > Good day to all, > Grégoire > "n is undefined" corresponds to text nodes. Grégoire |