Repository navigation
[🚀 Feature]: Rewriting Webdriver > Elements > Finders to Not Use HTML Snippet #2037
Description
Activity
@shbenzer, thank you for creating this issue. We will troubleshoot it as soon as we can.
Info for maintainers
Triage this issue by using labels.
If information is missing, add a helpful comment and then
I-issue-templatelabel.If the issue is a question, add the
I-questionlabel.If the issue is valid but there is no time to troubleshoot it, consider adding the
help wantedlabel.After troubleshooting the issue, please add the
R-awaiting answerlabel.Thank you!
I agree this page should be updated. We can use this web page to create example code and update documentation.
multiple web element examples are available - https://www.selenium.dev/selenium/web/formPage.htmlReacted by Titus Fortner- addeddocumentationImprovements or additions to documentationImprovements or additions to documentationhelp wantedExtra attention is neededExtra attention is neededgood first issueGood for newcomersGood for newcomers
on Oct 4, 2025 This issue is looking for contributors.
Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.
Hi @rpallavisharma @shbenzer
I would like to work on this issue. Can you please elaborate more about issue and change require?
ThanksThe current page uses a html snippet to showcase how finders work in selenium. The code examples could use a webpage , a link is shared on which this could be formed. Kindly read the comments shared on it.
@nooras if you still have questions feel free to join the selenium slack - selenium docs channel.
I would like to work on this issue
And I have reviewed the current Finders page and mapped the existing examples against formPage.html.
Most scenarios appear to have a straightforward equivalent on that page (ID, Name, Class Name, CSS selectors, finding elements from elements, collections, active element, etc.).
The only section I couldn't map cleanly is the Shadow DOM example, since formPage.html doesn't contain any shadow roots.Before I start working on a PR, would maintainers prefer that the Shadow DOM example:
- Move to a different test page (for example shadowPage.html, which already contains shadow roots), or
- Remain unchanged / be handled separately from this issue? Happy to proceed with the rest of the migration once I have guidance on that section.
@beinghumantester , you can use another webpage, preferably from selenium hosted pages to explain shadow dom, if it is part of this section. that should be alright to do. and thanks for the help.
- added a commit that references this issue
on Oct 8, 2026 - added a commit that references this issue
on Oct 8, 2026
Feature and motivation
As we move code examples to executable files and not as code snippets in the .mds themselves, how do we want to address this page?
Code examples are based on the HTML snippet, but do we want to use one of these instead?