> - Make sure you're setting the Content-Type header to "text/xml".
> - Probably don't need to use documentElement - try response =
> res.responseXML.documentElement || res.responseXML ;
> - The namespace declaration on the p element could be causing
> problems. Does it work without it? What about var p =
> response.getElementsByTagNameNS('*','p')[0]; ?Hamish, thanks for the advice -- still not there but getting closer. So here is what I know from using the Drosera debugger: - Safari is getting the response but there is no responseXML only a responseText so for some reason it appears to believe that what the server is sending isn't valid xml. - res.getAllResponseHeaders() looks like: Date: Sat, 29 Dec 2007 04:00:00 GMT Content-Length: 78 Server: CherryPy/3.0.2 Content-Type: text/xml So the Content-Type looks fine. - res.responseText has the value: <?xml version="1.0" standalone='yes'?><response><id>522</id><p>abc</p></response> which looks like fine XML to me. (I did drop the namespace declaration and the encoding to see if that made a difference - it didn't.) So I am stumped -- the content-type appears correct, the server appears to be sending valid xml but Safari only populates the responseText and not responseXML. Since I really do want to pass XML and manipulate it via DOM, I need to try to find out why Safari won't populate responseXML. Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
