|DOMParser (string and stream input source)||Available|
|Web Services with SOAP and WSDL||No longer available from Gecko 1.9/Firefox 3.|
|FIXptr and XPointer||Available since 1.4alpha in the core Mozilla. Moved to XML Extras during 1.4beta.|
Other test cases for each of the implemented components listed above exist in
extensions/xmlextras/tests/. More exhaustive test suites need to be created, however. If you'd like to help out with QA, you can do one of the following:
- Sign up as the QA owner for any of the implemented components. The QA owner will manage the tests associated with their component, act as QA contact for related bugs and help with regression testing.
- Contribute a test suite or individual tests that use the implemented components. File bugs for new test you have, and/or check them into
- File bugs against the implemented components. Bugs should be filed against the XML component in the Browser product.
Probably the best way to learn how to use these technologies is through examples. There are some in
extensions/xmlextras/tests/. If you follow that link to look at the examples you will need to look at page source for the HTML documents.
For XMLHttpRequest object you can mostly rely on the Microsoft XMLHttpRequest documentation, with some caveats: all functions and property names begin with a lower case letter and the object creation is different. Some properties are not implemented.
Thad Hoffman has written a document that shows how you can mimic XML Data Islands in Mozilla. Edmond Woychowsky has also written articles on XML Data Islands in Mozilla: "Make XML data islands work in Mozilla", "Build cross-browser XML paging code" and "Implement a flexible shopping cart with XML and ASP". The Mozilla Developer Center has several pages for XMLHttpRequest.
Below are some key differencies in "XML Extras" between Mozilla and Microsoft software:
|Member names||Case insensitive?||Begins with lower case letter|
||ok||ok starting with milestone 0.9.7 (actually nightly 2001-11-28). With older builds, passing strings to send() works only in chrome, see post.html sample. The "workaround" is to use DOMParser object's
|DOMParser Creation||not available||
|XMLSerializer Creation||not available||