You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry I couldn't reproduce this error locally. Probably I will need and HTML and JS for a page you are testing.
Maybe there are some JS hooks or non-native input fields that prevents a field from being cleared.
On second check you may be right. Implementation of clearField is quite different from fillField and didn't throw an error when field was not located. I updated that and added clearField to other helpers. Now it should locate elements by name, labels, css, xpath, and throw an error if no element matched. Just as you expected it to be )
Activity
DavertMik commentedon Dec 24, 2016
Sorry I couldn't reproduce this error locally. Probably I will need and HTML and JS for a page you are testing.
Maybe there are some JS hooks or non-native input fields that prevents a field from being cleared.
DavertMik commentedon Dec 24, 2016
On second check you may be right. Implementation of
clearFieldis quite different fromfillFieldand didn't throw an error when field was not located. I updated that and addedclearFieldto other helpers. Now it should locate elements by name, labels, css, xpath, and throw an error if no element matched. Just as you expected it to be )Thanks for the report.
mparpaillon commentedon Dec 26, 2016
It seems to break on Chrome only (on 0.4.13).
I'm testing via BrowserStack and no problem with IE11, Edge or Firefox... Just chrome.
Probably a bug with WebdriverIO
clearElementfunction ?