"Martijn" <[EMAIL PROTECTED]> wrote: > On 6/20/06, Foteos Macrides <[EMAIL PROTECTED]> wrote: >> IMHO we are still many years away from the day when the great majority of >> browsers actually in use will have the same serializer with both the >> behavior AND object names of a W3C standard, and even then there will be >> the >> issue of "heritage" documents on the web. Whatever one's personal >> feeling >> might be about one organization versus another, I don't see why one >> organization's "proprietary" objects should be considered sufficient. >> >> This is a "portability" issue, not a "capability" issue. > > Ok, so in that case, maybe you should raise this on the whatwg mailing > list? > You want a .xml property similar to the .xml property of Internet Exlorer, > then?
Martijn, This type of portability is basically a form of error handling. Generating a "standard" for IE's xml beyond what the Microsoft folks already offer would be kinda like closing the doors after the horse has left the barn. The Firefox innerHTML since Boris "fixed" it last year is much better than IE's or Opera's innerHTML when you look at the strings that are being generated, and closer to what you might expect if a consensus standard had been generated before it was implemented, particularly if you compare the outputs for HTML versus XHTML (with the XHTML served as text/html, and application/xhtml+xml indicated only in a meta tag so that IE doesn't force a download offer). But the really important thing is that since that bug "fix" I have not encountered anything on the web which was originally written for IE's (and Opera's) innerHTML which causes problems for Firefox. I suspect a similarly happy situation would materialize if Firefox treated var str = foo.xml as an instruction to assign the string from XMLSerializer's serializeToString(foo) to str, and I presume that would be trivial to implement. Regards, Fote -- _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
