Skip to content

restore throwing InvalidSelectorException after upgrading to Chrome 123#2700

Merged
asolntsev merged 1 commit intomainfrom
fix/invalid-locator-handling
Mar 29, 2024
Merged

restore throwing InvalidSelectorException after upgrading to Chrome 123#2700
asolntsev merged 1 commit intomainfrom
fix/invalid-locator-handling

Conversation

@asolntsev
Copy link
Copy Markdown
Member

I think it's a bug in Chrome: now it throws non-w3s-standard "javascript error: {"status":32,"value":"Unable to locate an element with the xpath expression //input[:attr='al] because of the following error:\nSyntaxError: Failed to execute 'evaluate' on 'Document': The string '//input[:attr='al]' is not a valid XPath expression."}" in case of invalid locator.

I think it's a bug in Chrome: now it throws non-w3s-standard "javascript error: {"status":32,"value":"Unable to locate an element with the xpath expression //input[:attr='al] because of the following error:\nSyntaxError: Failed to execute 'evaluate' on 'Document': The string '//input[:attr='al]' is not a valid XPath expression."}" in case of invalid locator.
@asolntsev asolntsev added this to the 7.2.3 milestone Mar 29, 2024
@asolntsev asolntsev self-assigned this Mar 29, 2024
@sonarqubecloud
Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@asolntsev asolntsev merged commit 57ac021 into main Mar 29, 2024
@asolntsev asolntsev deleted the fix/invalid-locator-handling branch March 29, 2024 11:11
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.

1 participant