-
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
Blur at end of setValue causes StaleElementReference #292
Comments
It is worse. We have text fields where you type in the field and do not press enter. The UI underneath fires off code to find matches of what you have typed (matching user names, group names, file names, whatever). But Doing I can't think how to work-around that. And I see that this auto-complete regression is discussed in the PR #286 |
Issue for workarounds in ownCloud: owncloud/core#32143 Acknowledgement: bits of code taken from the workaround mentioned in the comment at #286 (comment) - thanks @pfrenssen |
@phil-davis , that shouldn't be a problem if, in #286 discussion, we decide to return to original code prior to #244. |
If something can be done so that fillField/setValue ends up leaving focus on the field, then auto-complete has a chance... |
No |
@phil-davis Another option I've found on this is using javascript injection.
I found some inputs, specially using google places that there is no way of filling it with the dropdown. That behaviour is explained in 301 but it's basically the same problem. |
Alternative solution without JS:
This somewhat does the same as the setValue method. Please see that method if you need any changes (like keeping old texts etc). |
If
fillField
-setValue
is called with an input that makes the field go away, then the recent code that tries to do ablur
out of the field fails withStaleElementReference
e.g. put an ENTER at the end of the field. In ownCloud, when creating a new folder, a dialog pops up and you type the new folder name and press enter. The dialog disappears and the new folder is created. See:
owncloud/core#32143
After #286 the above sequence fails with
StaleElementReference
because the new code insetValue
tries to do a blur on the element after the data has been typed in the field, and the field has gone away.It is possible to workaround by catching and ignoring the
StaleElementReference
exception. But it would be nice if the exception was not thrown in the first place.The text was updated successfully, but these errors were encountered: