On 6/20/06, Foteos Macrides <[EMAIL PROTECTED]> wrote:
Apple is also using .innerHTML for browsers which implement it in that context (on Windows PCs, that includes Firefox and Opera), so here's another portability issue that might be of interest to you. Your implementation of innerHTML creates well-formed markup in that context, e.g., for responseXML.documentElement.innerHTML (with xmlns="http://www.w3.org/1999/xhtml";). Opera does not, but doesn't seem to care when you use the ill-formed markup it returned. IE's innerHTML also would be ill-formed, but can't be used in that context, e.g., responseXML.documentElement.innerHTML yields an error, perhaps because IE does care that the markup it created is ill-formed. However, IE offers an xml object, which is the homolog of the innerHTML object for that context, e.g., responseXML.documentElement.xml yields well-formed markup in IE, like Firefox's responseXML.documentElement.innerHTML. I don't know if you want to use the "de facto standard" rationale for this issue, but since you've already done it (and "properly") for innerHTML, it should now be a snap to make the equivalent available as an xml object.
So you want a .xml property for Mozilla? Note that you already can do: var s = new XMLSerializer(); var d = responseXML.documentElement; var str = s.serializeToString(d); alert(str); This was taken from: http://developer.mozilla.org/en/docs/XMLSerializer Regards, Martijn
Regards, Fote -- _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
_______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
