Consistent xpath for a single DOM element
DOM 3 XPath implemention and helper for node.js and the web
Pure JS implementation of the DOM Level 3 XPath specification
Search xml2js JSON documents with XPath query strings.
DSL for building complex XPath expressions
CSS to XPath
Converts CSS selectors to xpaths
Get the XPath from an HTML element
SaxonJS XSLT 3.0 processor: a conformant high-performance implementation of XSLT 3.0 for Node.js
Utility function for converting XPath expressions to CSS selectors
TypeScript helper functions to narrow the type of object to a Node descendant
Easy conditional if-else logic for your Cypress tests
SaxonJS XSLT 3.0 processor: command line interface to SaxonJS
A simple dapp used in MetaMask e2e tests.
DOM 3 and 4 XPath 1.0 implemention for browser and Node.js environment.
TypeScript definitions for xml-crypto
Create and evaluate simple XPath position expressions.
A netty server with uiautomator2 handlers
Wicked Good XPath
Xpath pure javascript implementation for node.js
A (Browser) Range implementation / wrapper with XPath features, extracted from Annotator
Easily use XPath to locate any element in an HTML DOM page
Exports `$`, `$$`, and `$x` utilities as described in Chrome Console Utilities API reference
Wrapper for browsers' XPath evaluator with added support for OpenRosa extensions.
backtrack-xpath accepts a REXML::Element and returns the full XPath back to the root.
Attempts to return the relative xpath for each element containing text.
A simple way of extracting various elements from an Nokogiri document using XPaths
== FEATURES: * takes an XML with actions from tg4w and outputs stand-alone Ruby code that can be run directly or embedded into existing code (e.g. for test automation). * can be used as a library or as an executable script. * takes the xpath from tg4w and uses only enough info to guarantee the uniqueness of the referenced element, allowing the generated script to keep working even with some change to page structure. == PROBLEMS: * the generated code is damn ugly. * a few action types from the XML input still aren't recognized. * some dependencies aren't very clearly sorted out yet. you might find you need something that is not specified. if yes, please report this as an issue in our issue tracker. * i don't know, find more and let me know =) == SYNOPSIS:
No description provided.
No description provided.