Well, I’m sure xPath is a lot more
flexible, but holy crap is that a lot of code. As I said, mine is limited, but
serves my purposes very well. And it’s generic enough for anyone to use,
although it only handles node types 1 to 3. Anything beyond that will be
ignored (or possibly break it, I haven’t tested it thoroughly against
other node types). http://www.devguru.com/Technologies/xmldom/quickref/obj_node.html#types
(node type information) Greg From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sam Thanks (a lot! ). I've had to rule
out including a 100Kb xPath.js library. Maybe this lib is a better
solution. I diagnosed the problem with IE
responseXML - if the file isn't served "up" as text/xml, IE doesn't
make responseXML available. (I was testing on my local hard-disk / no
server). Posting to a server solves this problem. I can (will) live
with that. Sam |
_______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs