[BUG] Page.click leads to 'Element has moved during the action'

[mxschmitt]

Context:

• Playwright Version: 0.15+
• Operating System: Docker / recommended image

Code Snippet

Still working on a small reproducible, but seems to be a bigger more rare edge case.

await page.click('.ant-picker-today-btn')

Describe the bug

In Playwright <= 0.14 the used snipped for clicking on an element has worked. In 0.15+ it leads to Element has moved during the action in around 80%+ of the cases.

Related PR: #1942
cc @dgozman

[jperl]

Is this error thrown only if the element moved to a place that is no longer clickable?

Hopefully the the click can be auto-retried by playwright, if the element moved somewhere that it is clickable.

[mxschmitt]

Issue could be fixed by adding a await page.waitForTimeout(100) before the actual click action. But that seems just like a workaround for me instead of fixing the actual issue.

Also wondered, why it was working in <= 0.14

[hlawuleka]

But why do we have to add a timeout? I mean is 100 the base number? What happens if you put 1? and why?. I ask because we might be hacking a bigger problem, which if not addressed may bite back.

[thernstig]

Just want to add that I have also seen this.

[clayrisser]

I am having this same issue. I am able to locate it just fine, but get the following error when clicking.

Element has moved during the action

[AutoSponge]

Sounds like you're racing the JS animation and rendering on the "today button" modal overlay container. The element gets rendered, waitFor resolves, animation moves and gradually makes visible the element/container, click attempts to engage.

[clayrisser]

@AutoSponge so how would I get the button to click? I do not have the ability to change the behavior of the button.

[AutoSponge]

@codejamninja The modal appears by animating opacity after placing the elements. You should wait for the modal to be visible.

[clayrisser]

Ok, thanks

[aslushnikov]

Still working on a small reproducible, but seems to be a bigger more rare edge case.

@mxschmitt so is this still relevant?

[mxschmitt]

Workaround was previously to use the text selector for that. But now its fixed, no clue which PR but its fixed now, yey.