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

Parentheses are removed from form element values #185

Open
bartfeenstra opened this issue Oct 13, 2014 · 8 comments
Open

Parentheses are removed from form element values #185

bartfeenstra opened this issue Oct 13, 2014 · 8 comments

Comments

@bartfeenstra
Copy link

When I use And I fill in "field[foo]" with "Acme (123)" to enter a value into a form field, Acme (123) becomes Acme 123). In short, the opening parenthesis is removed from the code. What may cause this? I tracked the stack down to Selenium2Driver::setValue() and there the value is still intact.

@aik099
Copy link
Member

aik099 commented Oct 13, 2014

Interesting that only opening brace, located in the middle of the text is stripped off. What was value in that field before new value is about to be set?

@bartfeenstra
Copy link
Author

The field was originally empty.

I am using version 1.1.1, by the way, due to our requirement on Behat 2.5.

I also wonder if this may be a collision with Drupal's autocomplete form elements, as I cannot reproduce this on non-Drupal sites, or even in a regular textfield rendered by Drupal.

@stof
Copy link
Member

stof commented Oct 13, 2014

if it only happens for Drupal's autocomplete fields, it is probably a conflict between the way WebDriver sets the value and the JS code of Drupal rather than a bug in Mink

@stof
Copy link
Member

stof commented Oct 13, 2014

btw, Mink 1.6 is compatible with Behat 2.5. You are not forced to use Mink 1.5 and MinkSeleniumDriver 1.1.1

@bartfeenstra
Copy link
Author

Thanks! We use https://packagist.org/packages/drupal/drupal-extension, which is a little crufty (hope to help clean it up soon) and requires Mink 1.5.

@stof
Copy link
Member

stof commented Oct 13, 2014

@bartfeenstra IMO, it is just a matter of sending them a PR to update their version constraint to allow the new Mink version

@bartfeenstra
Copy link
Author

The exact same issue occurs when using Mink 1.6.

@stof
Copy link
Member

stof commented Oct 13, 2014

Does Drupal's autocomplete behavior perform something special for ( chars ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants