angular.js/src/ng/directive, branch v1.2.7 fix(ngRepeat): allow for more flexible coding style in ngRepeat expression 2014-01-03T00:14:16+00:00 Gias Kay Lee 2014-01-02T16:22:10+00:00 c9705b755645a4bfe066243f2ba15a733c3787e1 With this change it's possible to split the ng-repeat expression into multiple lines at any point in the expression where white-space is expected. Closes #5537 Closes #5598 
With this change it's possible to split the ng-repeat expression into multiple
lines at any point in the expression where white-space is expected.

Closes #5537
Closes #5598
fix(input): use apply on change event only when one isn't already in progress 2013-12-31T08:41:15+00:00 Igor Minar 2013-12-31T08:40:53+00:00 a80049fd0ac858eeeb645a4209cb2a661d0b4c33 Closes #5293 
Closes #5293
fix(input): prevent double $digest when using jQuery trigger. 2013-12-30T23:09:49+00:00 Michał Gołębiowski 2013-12-05T13:59:13+00:00 1147f21999edf9a434cd8d24865a6455e744d858 If an event was performed natively, jQuery sets the isTrigger property. When triggering event manually, the field is not present. Manually triggered events are performed synchronously which causes the "$digest already in progress" error. Closes #5293 
If an event was performed natively, jQuery sets the isTrigger property.
When triggering event manually, the field is not present. Manually
triggered events are performed synchronously which causes the "$digest
already in progress" error.

Closes #5293
docs(ngCloak): style name is ng-cloak, not ngCloak 2013-12-19T13:32:19+00:00 snicolai 2013-12-12T03:49:52+00:00 9865a7c0ad678fa6a3daa2719e37d94aeb62f67b Closes #5374 
Closes #5374
docs(booleanAttrs): add @priority to all the boolean directives 2013-12-19T13:29:19+00:00 Mark Jones 2013-12-10T21:35:12+00:00 efba4731e4b22481f1c0b1c417ea24c00182095a Closes #5361 
Closes #5361
docs(ngEventDirs): adding quick examples for new events 2013-12-19T12:57:33+00:00 James Watling 2013-12-09T20:53:35+00:00 3d156a76e3501ea29fe7d208dc89f0ae89e76fc3 Closes #5338 
Closes #5338
docs(ngInit): fix typo 2013-12-18T21:14:46+00:00 Jason Farnsworth 2013-12-10T01:16:54+00:00 040e743b393f53aad11ce200de21590b4fcb0b8b Closes #5343 
Closes #5343
fix(input): do not hold input for composition on android 2013-12-18T20:28:07+00:00 Chia-liang Kao 2013-12-18T08:28:35+00:00 3dc18037e8db8766641a4d39f0fee96077db1fcb Workaround for chrome for android until #2129 is ready. Closes #5308, #5323 
Workaround for chrome for android until #2129 is ready.

Closes #5308, #5323
fix(select): invalidate when 'multiple`, `required` and model is `[]` 2013-12-17T13:10:40+00:00 Caitlin Potter 2013-12-07T23:22:04+00:00 5c97731a22ed87d64712e673efea0e8a05eae65f When `multiple` attribute is set on a `<select>` control and the model value is an empty array, we should invalidate the control. Previously, this directive was using incorrect logic for determining if the model was empty. Closes #5337 
When `multiple` attribute is set on a `<select>` control and the model value is an empty array,
we should invalidate the control.  Previously, this directive was using incorrect logic for
determining if the model was empty.

Closes #5337
docs(ngIf): remove invalid comment from CSS 2013-12-17T11:59:29+00:00 Pete Bacon Darwin 2013-12-17T11:59:29+00:00 4f724333923c7eb46dbef595b2fd9ccf86b8db39 We cannot use valid /* ... */ CSS comments in examples because they break the parsing of the ngdoc comments. We can't use inline // comments because these are not valid in CSS. We could use the //!annotate extension to the ngdoc parser but this does not seem to be working. It is best to simply remove this line. Closes #5234 
We cannot use valid /* ... */ CSS comments in examples because they break the parsing
of the ngdoc comments.  We can't use inline // comments because these are not valid in
CSS.

We could use the //!annotate extension to the ngdoc parser but this does not seem to be
working.  It is best to simply remove this line.

Closes #5234