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
When there's a form element using AngularStrap's bs-datepicker autofill-event causes the element to be marked as dirty, Angular then sees the form as dirty too. Depending on the timing, the date may show as dirty immediately or only after you click on another field or two. Plunker showing this is here: http://plnkr.co/edit/gYPSOaXARoHiCrkeTAjh?p=preview
Also seen with Angular 1.2.6 and with Angular-Strap 2.1.1. Firefox 32.0.3 & Chrome 37
Just guessing but somehow autofill-event is seeing the instantiation of the bs-datepicker element as an autofill event?
The text was updated successfully, but these errors were encountered:
When there's a form element using AngularStrap's bs-datepicker autofill-event causes the element to be marked as dirty, Angular then sees the form as dirty too. Depending on the timing, the date may show as dirty immediately or only after you click on another field or two. Plunker showing this is here:
http://plnkr.co/edit/gYPSOaXARoHiCrkeTAjh?p=preview
Also seen with Angular 1.2.6 and with Angular-Strap 2.1.1. Firefox 32.0.3 & Chrome 37
Just guessing but somehow autofill-event is seeing the instantiation of the bs-datepicker element as an autofill event?
The text was updated successfully, but these errors were encountered: