I just took a quick glance at the code, and I have to say that it's not surprising that it has broken in Firefox. Here's a revealing comment:
//Code to make Mozilla DOM documents act more like MS DOM documents. It basically attempts to extend the prototype of either XMLDocument or Document objects in Firefox to make it behave more like IE. This is dangerous, as one cannot safely assume that native objects may be extended arbitrarily, and evidently, the behaviour of the native XMLDocument and Document objects in Firefox has changed since 2006. Furthermore, I think that the strategy of attempting making Firefox behave like IE for handling XML documents is an interesting one, as I believe most other js libraries treat IE as the special case. In the case of handling XML documents, Firefox, Opera, Chrome and Safari all expose virtually identical APIs for parsing XML (and transforming it with XSLT). I wrote my own browser XML/XSLT compatibility layer recently, after failing to find a library being maintained. I can't really recommend it for use by others, as it lives as a part of a larger project, and I haven't had time to break it out into its own library, but it might serve as a useful starting point for you. The relevant code lives here: https://svn.apache.org/repos/asf/commons/sandbox/gsoc/2010/scxml-js/trunk/src/javascript/scxml/cgf/util/ Cheers, Jake On Fri, May 13, 2011 at 9:04 AM, Jacob Beard <[email protected]> wrote: > It looks like zxml hasn't been updated since 2006. Web browsers are a > rapidly moving target, so it is possible that this library is no > longer compatible with modern browsers. > > If you like, though, you could post a reduced test case online. This > will make it easier for other people to determine where this is > failing. > > Jake > > On Fri, May 13, 2011 at 8:22 AM, hguser <[email protected]> wrote: >> Hi: >> We are using the zml in our project for ajax request,it works well in >> IE,however when I use the firefox,I will get a error: >> >> setting a property that has only a getter >> >> And after I found that it is this code which result in the error: >> >> oMozDocument.prototype.readyState = 0 >> >> So,how to fix it? >> >> -- >> To view archived discussions from the original JSMentors Mailman list: >> http://www.mail-archive.com/[email protected]/ >> >> To search via a non-Google archive, visit here: >> http://www.mail-archive.com/[email protected]/ >> >> To unsubscribe from this group, send email to >> [email protected] >> > -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
