Skip to content

Conversation

@harsha509
Copy link
Member

@harsha509 harsha509 commented Apr 19, 2021

Description

Allow RelativeBy to work with findElement.

  • Returns: first resolved element from array of elements
  • throws: NoSuchElementError if no element is found

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the contributing document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@AutomatedTester AutomatedTester merged commit 68f3edc into SeleniumHQ:trunk Apr 20, 2021
pujagani pushed a commit to pujagani/selenium that referenced this pull request Apr 21, 2021
* [JS] Allow relativeby with findElement

* [js] resolves custom locator issue triggered by previous change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants