[Question] elementHandle.waitForSelector followed by elementHandle.waitForElementState
See original GitHub issuewaitForSelector could be followed by a waitForElementState to e.g. make sure that an element is not moving, using the stable
state.
Is this always the required workflow to achieve this, or was there ever an idea that waitForSelector
could also somehow wait for the element to become stable?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
ElementHandle | Playwright
The method finds an element matching the specified selector in the ElementHandle 's subtree. If no elements match the selector, returns null ....
Read more >Looking for a child element within ElementHandle with waitFor
It seems you need not Object.values() for the docsPanels : it is an array and you can iterate over it as is. You...
Read more >Use waitForElementState in Playwright Internal With Examples
Learn how to use waitForElementState function in Playwright Internal framework for your next JavaScript automation project with LambdaTest Automation ...
Read more >Playwright changelog - Awesome Node.js - LibHunt
#2974 - [BUG] Unable to adopt element handle from a different document #3122 - [QUESTION] Chromium versions are mismatched in docker, leading to...
Read more >ElementHandle.waitForSelector() method - Puppeteer
waitForSelector (), this method does not work across navigations or if the element is detached from DOM. Signature:. class ElementHandle {
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this was more of semantics i.e. is it a good idea for waitForElement() to be able to wait for something to be stable. I.e. in a screenshot scenario.
I’ll close this as a part of the bug triaging process. We have hundreds of bugs and feature requests with dozens and even hundreds of upvotes, while this one only has a few thumbs up. Please feel free to open a new bug and link this one if you’d like to see it addressed.