Extracts WebElements based on different criteria. The input can either be a WebDriver (representing a browser's window), or a WebElement (a subpart of the window). The following search criteria are available:
|className||Finds elements based on their
|cssSelector||Finds elements based on a CSS selector expression.|
|id||Finds an element based in its
|linkText||Finds links through an exact match of their text.|
|name||Finds elements based on their
|partialLinkText||Finds links by a partial match of the given text.|
|tagName||Finds elements based on their tag names.|
|xpath||Finds elements based on an XPath expression.|
For each extracted WebElement a new row is added to the output table.
Note that you cannot only search within the given input, but also navigate the entire DOM tree.
For example, you can use the XPath query
.. to find a WebElement's parent.
In case you need to extract an element which is not immediately available on the page, consider specifying an Implicit wait within the Start WebDriver's Timeouts options.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to email@example.com, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.