angular.js/src, branch v1.0.2 revert: fix(ng-repeat) to work with primitive types 2012-08-31T20:44:36+00:00 Igor Minar 2012-08-31T20:43:57+00:00 0e1545eb04f217f24ecd4e1474cf4cb31c8c3ef0 this commit was accidentaly merged. it needs more work and we don't have CLA signature This reverts commit 98d489712eff7559bce87ae53bd242112a875c1a. 
this commit was accidentaly merged. it needs more work and we don't
have CLA signature

This reverts commit 98d489712eff7559bce87ae53bd242112a875c1a.
fix(docs): indicate support for passing a string as the `controller` property on $routeProvider's route object 2012-08-31T05:38:53+00:00 Brice Burgess 2012-07-18T19:21:03+00:00 c28123a8727904d0febe509f9c81e8b54471ccb6 






fix(ng-repeat) to work with primitive types
2012-08-31T04:34:41+00:00

Zhenbo Zhang

2012-05-08T21:00:38+00:00

98d489712eff7559bce87ae53bd242112a875c1a












fix(mocks): free up memory after every spec
2012-08-30T23:53:52+00:00

Vojta Jina

2012-08-30T21:42:46+00:00

8fa2bb72bc010c9967f41e2ba80088d7ed413e37












fix(jqLite): better support for xhtml
2012-08-30T17:52:36+00:00

Igor Minar

2012-08-29T11:01:13+00:00

bb9badeb2a53698218ef891e7ae6d0e3a810fe9b

it turns out that some stuff doesn't work in xhtml as it does in html.

for example   can't be innerHTML-ed and auto-closing of elements
doesn't work.

the reporter of the referenced issue claimed that innerHTML vs text on
script made a difference but that doesn't appear to be true in my testing.

I'm not including test for this because testacular doesn't currently
run tests in xhtml yet.

Closes #1301





it turns out that some stuff doesn't work in xhtml as it does in html.

for example   can't be innerHTML-ed and auto-closing of elements
doesn't work.

the reporter of the referenced issue claimed that innerHTML vs text on
script made a difference but that doesn't appear to be true in my testing.

I'm not including test for this because testacular doesn't currently
run tests in xhtml yet.

Closes #1301







doc($log): correct non-working example
2012-08-28T04:20:51+00:00

Misko Hevery

2012-06-12T17:01:43+00:00

300c5c0c99eb65fb9052e64bf86d00c0aa7988df












fix(ng-list): remove data bound flicker
2012-08-28T04:20:50+00:00

Misko Hevery

2012-06-01T21:58:51+00:00

2af0348cea016e7081eab3189ae89f13f0e08213












docs(a): expose hidden docs
2012-08-24T21:59:52+00:00

Igor Minar

2012-08-20T15:32:01+00:00

cd7e58ba41eb886be2195e886f57521c568cb0a4

It seems that docs for these directive were previously hidden by accident





It seems that docs for these directive were previously hidden by accident







docs(ngRoute): fix typo
2012-08-24T21:59:43+00:00

johnlindquist

2012-08-23T19:02:31+00:00

9391475dc3bad03895fcf277f57422d64bd38ef5

aftre -> after





aftre -> after







fix($compile): denormalize directive templates
2012-08-13T21:35:32+00:00

Igor Minar

2012-08-11T07:13:10+00:00

7d77de283404d486ae3b21df69704894905ff8a7

Since developers are allowed to customize start/end interpolation
strings, but third-party directive creators don't know about these
customizations, we should standardize on {{ }} in templates of
reusable (third-party) directives. During the compilation, these
templates are then denormalized to use whatever the custom
start/end symbol is, effectively translating the template into the
syntax of the runtime environment.

This addresses an issue raised at http://goo.gl/e8VPV

Existing code should not be affected by this change since project
that do use custom interpolation markers are not expected to use
{{ }} in existing directive templates.





Since developers are allowed to customize start/end interpolation
strings, but third-party directive creators don't know about these
customizations, we should standardize on {{ }} in templates of
reusable (third-party) directives. During the compilation, these
templates are then denormalized to use whatever the custom
start/end symbol is, effectively translating the template into the
syntax of the runtime environment.

This addresses an issue raised at http://goo.gl/e8VPV

Existing code should not be affected by this change since project
that do use custom interpolation markers are not expected to use
{{ }} in existing directive templates.