I'm hitting a wall in making ng-model and ng-switch play nice together. It is *not* an issue of "but ng-switch has isolate scope" - everything preserves it's 2-way-binding the whole time.
Where is $dirty status lost in here(plnkr!)<http://plnkr.co/edit/wOVTZOxMZ5mrs0c2eLHB?p=preview> and how could I keep it? The plunker is probably self-explanatory, but there is 3 different setups for using tab-like constructs(with ng-switch) with forms. In my opinion every one should preserve their pristine status navigating to other tab and back. It does not. *Remarks*: - Seems like deleting and recreating the elements is the devil. Any ideas for the workaround? - Probably something to do with the default values of the input/form directives which are not checked in the creation? I'm lost, guys. Maybe anyone could point out the mistake I'm making - link to original stackoverflow question<http://stackoverflow.com/questions/23442295/form-and-input-dirty-attribute-in-ng-switch> . -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
