Form's state is pristine, although all checkboxes are selected

[Nadia Markadoni]

Here is a jsfiddle of what i am trying to do:

http://jsfiddle.net/BnHmv/

I have a list of checkboxes and  "select all"/"unselect all" links which make all check boxes selected or not, but form state remains pristine.

In case of clicking on a single item state of form changes

[Nadia Markadoni]

here is a simpler example of the problem i am facing: http://jsfiddle.net/f5scR/

Why form's state does not change when chechbox's value is changing through a ng-click function?

[Peter Bacon Darwin]

Hi Nadia,

The answer is that the pristine state is only changed when the input itself updates the model, not when you update the model programmatically.  This makes sense because otherwise, when you set the value of the model initially it would make the input dirty straight away.

If you want to make the input dirty programmatically you need to get hold of the input's ngModelController.  The easiest way to do this, without writing a directive, is to note that by giving the form and the input's names they appear on the scope.  So in the case of the following fiddle: scope.myForm.value1.  Then you can do things like:

scope.myForm.value1.$setViewValue(...); // which will update the value and trigger the validation and dirty the input

or

scope.myForm.value1.$setDirty();

Here is the fiddle:

http://jsfiddle.net/u9Ant/

--
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 angular+u...@googlegroups.com.
To post to this group, send email to ang...@googlegroups.com.
Visit this group at http://groups.google.com/group/angular?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Anjo Krank]

I'm probably confused but how can you unit test such a controller? The form won't be there without the mark up, will it?

Cheers, Anjo

[Peter Bacon Darwin]

You can mock up the formController and the ngModelController and with a spy on $setViewValue and check that it gets called.

Alternatively you hide all this in a directive on the ng-click element where you pass in the name of the input in question.

http://jsfiddle.net/xaYy8/