DOM/XPath Generator: Difference between revisions

Jump to navigation Jump to search
Line 39: Line 39:
namespace resolver (assuming that we need to handle XML to be future proof)." -- Alex Hecht
namespace resolver (assuming that we need to handle XML to be future proof)." -- Alex Hecht


[http://verbosio.mozdev.org Verbosio] would be able to translate a XPath for a document it's editing into a XPath for a XUL tree (a la DOM Inspector) representing the document's structure.  This would be through simple text replaces.  Thus, a node found in the master document would easily translate to a XUL tree item.
[http://verbosio.mozdev.org Verbosio] would be able to translate a XPath for a document it's editing into a XPath for a XUL tree (a la DOM Inspector) representing the document's structure.  This would be through simple text replacements.  Thus, a node found in the master document would easily translate to a XUL tree item.


Shane Caraveo at ActiveState is working to develop a XUL unit test extension that would work in a similar fashion to Selenium and Selenium Recorder.  This consists of recording DOM events, and saving an xpath to the event target so the target can found and used to replay an event.  Exploratory code is in [https://bugzilla.mozilla.org/show_bug.cgi?id=323938 bug 323938].
Shane Caraveo at ActiveState is working to develop a XUL unit test extension that would work in a similar fashion to Selenium and Selenium Recorder.  This consists of recording DOM events, and saving an xpath to the event target so the target can found and used to replay an event.  Exploratory code is in [https://bugzilla.mozilla.org/show_bug.cgi?id=323938 bug 323938].
1

edit

Navigation menu