angular.js/docs, branch v1.0.0rc4 chore(docs): add nonminified jquery debug version of docs 2012-04-05T18:33:42+00:00 Igor Minar 2012-04-05T16:53:36+00:00 0f2de12273c50729e918c3103d92fdec6b5b3cad 






docs(tutorial): update tutorial intro + steps 0-3
2012-04-04T22:59:18+00:00

Igor Minar

2012-04-02T15:32:30+00:00

53b2254ea70019937463d8e079e1991b3d3d1d8b

also contains all kinds of fixes that I had to make in the docs app to
get the tutorial to render correctly





also contains all kinds of fixes that I had to make in the docs app to
get the tutorial to render correctly







chore(docs): restore old tutorial ngdoc files
2012-04-04T22:59:18+00:00

Igor Minar

2012-03-30T21:02:26+00:00

6336b6e89e3a80aec3c4367ab4c2737fd365c030












fix(docs): remove ngModelInstant from all examples
2012-04-04T22:56:15+00:00

Igor Minar

2012-04-04T22:56:12+00:00

fdf17d729fa7651e88dc5f27c40b8de875a34a55

just fixing leftover code after the removal of ngModelInstant





just fixing leftover code after the removal of ngModelInstant







feat(ngModel): update model on each key stroke (revert ngModelInstant)
2012-04-03T17:10:44+00:00

Vojta Jina

2012-03-30T19:07:19+00:00

06d0955074f79de553cc34fbf945045dc458e064

It turns out that listening only on "blur" event is not sufficient in many scenarios,
especially when you use form validation you always had to use ngModelnstant
e.g. if you want to disable a button based on valid/invalid form.

The feedback we got from our apps as well as external apps is that the
ngModelInstant should be the default.

In the future we might provide alternative ways of suppressing updates
on each key stroke, but it's not going to be the default behavior.

Apps already using the ngModelInstant can safely remove it from their
templates. Input fields without ngModelInstant directive will start propagating
the input changes into the model on each key stroke.





It turns out that listening only on "blur" event is not sufficient in many scenarios,
especially when you use form validation you always had to use ngModelnstant
e.g. if you want to disable a button based on valid/invalid form.

The feedback we got from our apps as well as external apps is that the
ngModelInstant should be the default.

In the future we might provide alternative ways of suppressing updates
on each key stroke, but it's not going to be the default behavior.

Apps already using the ngModelInstant can safely remove it from their
templates. Input fields without ngModelInstant directive will start propagating
the input changes into the model on each key stroke.







Doc fixes in bootstrap
2012-04-03T14:07:49+00:00

Brad Green

2012-04-03T14:07:41+00:00

28ff7c3a66fbd770515273c7ca2fcb9cd936b50e

Now makes sense.





Now makes sense.







fix(docs): update the example widget regexp for detecting angular.js url
2012-03-29T23:10:40+00:00

Igor Minar

2012-03-29T23:10:04+00:00

fc52b81d5288897b351397cd5a21aa98a54cca70

so that we don't show angular-cookies instead of angular.js





so that we don't show angular-cookies instead of angular.js







fix(docs): properly rewrite urls in doc examples at docs-next
2012-03-29T23:10:40+00:00

Igor Minar

2012-03-29T22:38:04+00:00

423242017e56c103b07b7f576dbd52a5a38c331a












chore(ngCookies): moved to module
2012-03-28T18:16:36+00:00

Misko Hevery

2012-03-26T23:22:06+00:00

7b22d59b4a16d5c50c2eee054178ba17f8038880












chore(resource): moved to module
2012-03-28T18:16:36+00:00

Misko Hevery

2012-03-27T04:45:38+00:00

798bca62c6f64775b85deda3713e7b6bcc7a4b4d