Skip to content
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

Function dragTo() won't work in v1.7.0. #376

Open
nagyad opened this issue Dec 12, 2023 · 4 comments
Open

Function dragTo() won't work in v1.7.0. #376

nagyad opened this issue Dec 12, 2023 · 4 comments

Comments

@nagyad
Copy link

nagyad commented Dec 12, 2023

After the v1.7.0 release our automated tests started to fail where we use the dragTo() because on first try it doesn't seem to do anything, but on second execution (executing the same step right after) it successfully moves the element.
Right after downgrading to v1.6.0 the problem disappeared.
Selenium version: selenium/standalone-chrome:4.1.3-20220405

@stof
Copy link
Member

stof commented Dec 12, 2023

Do you have a reproducer for that ? It would make it easier to debug the problem.

@nagyad
Copy link
Author

nagyad commented Dec 12, 2023

Our test case is a Drupal functional test which drags multi-value field values in a widget, not sure how relevant is that in this case.
The part in question:
// Edit the node to reorder field items.
$this->drupalGet($node->toUrl('edit-form'));
$handle = $this->assertSession()->elementExists('css', 'table#featured-media-field-values > tbody > tr:nth-child(1) a.tabledrag-handle');
$target = $this->assertSession()->elementExists('css', 'table#featured-media-field-values > tbody > tr:nth-child(2) a.tabledrag-handle');
$handle->dragTo($target);
$this->assertSession()->assertWaitOnAjaxRequest();

Which runs just fine, but the assertions after fail, since the $handle->dragTo($target); didn't work correctly.

@stof
Copy link
Member

stof commented Dec 12, 2023

Could you try bisecting which commit between 1.6.0 and 1.7.0 introduces the failure ? Without a reproducer, I cannot do it myself.

@nagyad
Copy link
Author

nagyad commented Dec 12, 2023

It fails with this commit: affb7ea and after. With the previous commits, it works just fine.

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

No branches or pull requests

2 participants