-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[page.click] Node is either not visible or not an HTMLElement #1990
Comments
The But, if it is visible when doing the (Hi Lei 😄) |
Looks like a bug. Does |
I also experienced this now. But it is intermittent. This is my code that fails on this: await page.click('#menu-toggle');
await page.click('tree-item >> text=App Name');
|
Could anyone share a complete repro script please? Otherwise, we can keep guessing what the issue is 😄 |
Hi Guys, after I change |
have a try |
Very interesting! The difference between |
I have checked it's unique string in the whole page source. then it can work the same with |
I have a hard time sharing a repro of my code, since it is a private project with a lot of code in it. I´ve always used Wild guess: Does it have something to do with that the menu in my case is animating with the combination of the css shadow dom selector and then the text in the shadow dom, and that the text contains spaces. (Ok I just realized that "guess" did not help at all). |
@dgozman @pavelfeldman I believe this has been fixed in 0.16.0. Is it possible that #2047 fixed this? I've tested the test case we have multiple times now and never gotten the failure again, whilst I got it frequently before 0.16.0. |
That's wonderful! It might be #2047 or #2020 or any other improvement 😄 |
Context:
Playwright Version: 0.15.0
Operating System: Ubuntu 18.04.4
Code Snippet
Describe the bug
when try to click the element ('text=add_profile_test'), it reports 'Node is either not visible or not an HTMLElement'.
but if I add one line
page.waitFor(1000)
beforeawait page.click('text=add_profile_test')
, then it can work, I don't understand why. Shouldn't waitForSelector and waitFor function work for this?The text was updated successfully, but these errors were encountered: