-
Notifications
You must be signed in to change notification settings - Fork 163
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
fillField with "\n" at the end results into NoSuchElement Exception #268
Comments
Can you give us the stack trace of the exception to allow us knowing at which point this is triggered ? |
sorry for not sending it directly
|
Are you sure, that element you send text into isn't removed after ENTER is pressed on it (e.g. form submitting and thank you page replaces current page without redirect)? |
yes, the element is removed after the field is submitted. Does "setValue" expect it still being there after setting the value? Occasionally I get a similar problem in an other place:
This only happens occasionally. So I thought first that the input field is not there before I do the |
The only change, that was made to |
I think in the current master the TAB is not send 67c5b8a |
Then it was changed to direct triggering of Still original problem (enter sending breaks stuff) remains mystery to me. |
When sending "\n", or Key::ENTER at the end of a string with fillField, the field is correctly filled and ENTER is pressed, but then it explodes with this Exception:
This used to work fine with 1.3.1 but does not with current master
my workaround is to catch
\WebDriver\Exception\NoSuchElement
and just do nothing, because actually all what I need did happenThe text was updated successfully, but these errors were encountered: