Confirmed users
146
edits
DOM/XPath Generator: Difference between revisions
m
→Potential Use Cases
m (→Use Cases) |
|||
| Line 26: | Line 26: | ||
https://bugzilla.mozilla.org/show_bug.cgi?id=208500 | https://bugzilla.mozilla.org/show_bug.cgi?id=208500 | ||
Copy XPath of node in DOM Inspector (not implemented yet) | Copy XPath of node in DOM Inspector (not implemented yet) | ||
(From WeirdAl's weblog) | |||
http://xpath.alephzarro.com/index | |||
XPather, a current implementation as an extension | |||
(From WeirdAl's weblog) | |||
http://annozilla.mozdev.org/ | |||
"My annozilla extension is a client for the W3C's Annotea server, which uses XPointers. I guess that XPointer generation/resolution would be easier with build-in XPath support." -- Matthew Wilson | |||
[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 replaces. Thus, a node found in the master document would easily translate to a XUL tree item. | ||