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
Combining my own experience with this problem with a couple of apparently related reports: protractor #2019 and angular #6250, I think the root cause is a conflict between WebDriver's sendkeys method and Angular's two-way binding.
A relatively minimal, hopefully reproducible, testbed is available at rapropos/twowaybind-sendkeys. This also demonstrates a potential workaround for certain situations: eschewing two-way binding using [(ngModel)] in favor of binding to a form control using [ngFormControl], which fixes the problem for me.
Version information:
webdriver 2.48.2
chromedriver 2.20.353124
chrome 47.0.2526.111
The text was updated successfully, but these errors were encountered:
I am now unable to reproduce this with RC2/RC3. I think the issues has been fixed. Please open a new bug if you can show us a reproducible test case. Thanks!
Combining my own experience with this problem with a couple of apparently related reports: protractor #2019 and angular #6250, I think the root cause is a conflict between WebDriver's sendkeys method and Angular's two-way binding.
A relatively minimal, hopefully reproducible, testbed is available at rapropos/twowaybind-sendkeys. This also demonstrates a potential workaround for certain situations: eschewing two-way binding using
[(ngModel)]
in favor of binding to a form control using[ngFormControl]
, which fixes the problem for me.Version information:
webdriver 2.48.2
chromedriver 2.20.353124
chrome 47.0.2526.111
The text was updated successfully, but these errors were encountered: