question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wait For Element State 'hidden' results to locator.elementHandle failed

See original GitHub issue

Describe the bug Since v10.0.0, RfBrowser fails at executing

Wait For Element State    ${selector}    hidden

playwright-log.txt:

{"level":30,"time":"2021-10-29T03:13:27.009Z","pid":31180,"hostname":"dummy_hostname","msg":"Strict mode is disbaled, return first Locator: css=td.loading-state in page."}
2021-10-29T03:13:27.009Z pw:api => locator.elementHandle started
2021-10-29T03:13:27.010Z pw:api waiting for selector "css=td.loading-state >> nth=0"
2021-10-29T03:13:37.014Z pw:api <= locator.elementHandle failed

Expected behavior In v9.0.2, the keyword is executing as expected playwright-log.txt:

{"level":30,"time":"2021-10-29T03:47:22.304Z","pid":31112,"hostname":"dummy_hostname","msg":"Page|Frame|Element resolved elementSelector: css=td.loading-state"}
2021-10-29T03:47:22.305Z pw:api => page.$ started
2021-10-29T03:47:22.305Z pw:api     finding element using the selector "css=td.loading-state"
2021-10-29T03:47:22.309Z pw:api <= page.$ succeeded
2021-10-29T03:47:22.309Z pw:api => page.waitForSelector started
2021-10-29T03:47:22.310Z pw:api waiting for selector "css=td.loading-state" to be hidden
2021-10-29T03:47:22.332Z pw:api <= page.waitForSelector **succeeded**

Desktop (please complete the following information):

  • OS: Windows, Linux (via WSL)
  • Browser: Chrome

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:12 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
emakaaycommented, Nov 14, 2021

Seems that 10.0.3 fixed all my problems. No need for additional issue

1reaction
emakaaycommented, Oct 29, 2021

Thanks @aaltat

The 10.0.2 release fixed the problem. At least for the first project tested 😁

Great stuff

Read more comments on GitHub >

github_iconTop Results From Across the Web

Expect assertions can't be used due to returning ... - GitHub
waitFor() . One problematic thing I've found is that locator. waitFor() errors if the Locator has matched multiple elements. This causes a strict-mode ......
Read more >
Playwright how to wait for locator that matches multiple ...
I've got a working solution now (looping round getting the hidden state of all elements and waiting till they are all true, or...
Read more >
Locator | Playwright - CukeTest
Locator represents a view to the element(s) on the page. ... Wait for initiated navigations to either succeed or fail, unless noWaitAfter option...
Read more >
Playwright.Locator — playwright v0.1.17-preview-3 - HexDocs
Use Playwright.Page.Mouse to click in the center of the element. Wait for initiated navigations to either succeed or fail, unless option: no_wait_after is...
Read more >
Browser - MarketSquare
If strict mode is true and locator finds multiple elements from the page, keyword will fail. If keyword finds one element, keyword does...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found