angular.js/test/ng/directive, branch v1.0.4 fix(ngSwitch): don't leak when destroyed while not attached 2013-01-18T08:03:42+00:00 danilsomsikov 2013-01-11T17:21:13+00:00 89303fd2dccb780bea594b16b8ec85d9f3bd8f92 The leak can occur when ngSwich is used inside ngRepeat or any other directive which is destroyed while its transcluded content (which includes ngSwitch) is not attached to the DOM. Refactor ngSwitch to use controller instead of storing data on compile node. This means that we don't need to clean up the jq data cache. Controller reference is released when the linking fn is released. Closes #1621 
The leak can occur when ngSwich is used inside ngRepeat or any other
directive which is destroyed while its transcluded content (which
includes ngSwitch) is not attached to the DOM.

Refactor ngSwitch to use controller instead of storing data on compile
node. This means that we don't need to clean up the jq data cache.
Controller reference is released when the linking fn is released.

Closes #1621
fix(ngRepeat): correctly apply $last if repeating over object 2013-01-17T08:25:07+00:00 Pete Bacon Darwin 2013-01-11T12:47:38+00:00 ed2fd2d0caad4e4b45f79bb39fd2a8b03fea8faa If the $last property is calculated from the original collectionLength on an object and properties starting with $ were filtered out, then $last is never applied and $middle is applied erroniously. Closes #1789 
If the $last property is calculated from the original collectionLength
on an object and properties starting with $ were filtered out, then $last
is never applied and $middle is applied erroniously.

Closes #1789
fix(select): support optgroup + select[multiple] combo 2012-12-05T01:21:31+00:00 _pants 2012-11-29T16:46:51+00:00 54c0d464b0f34f9bfd076883a6a78cf5925bd975 Closes #1553 
Closes #1553
fix(ngRepeat): support mostly-stable repeating for primitives 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:43:30+00:00 cde2f1a868ffacdc592803358130587fd73aca7b I'm reverting changes that were originally done to ngRepeat to fix #933, because these are now not necessary after the previous changes to keep ngModel always synced with the DOM. 
I'm reverting changes that were originally done to ngRepeat to fix #933,
because these are now not necessary after the previous changes to keep
ngModel always synced with the DOM.
test(ngRepeat): clean up and improve tests 2012-11-26T19:39:10+00:00 Igor Minar 2012-11-23T15:08:47+00:00 6e2c38f54dc012dc919cdd7f7ab9b73dc1e99c66 






test(ngRepeat): add test for issue #1076
2012-11-26T19:38:51+00:00

Igor Minar

2012-11-26T19:17:11+00:00

ff4b3e20c1bcf8f4c76114f5537c8857393c9b2b












fix(select): select option with a label of 0 is not shown
2012-10-31T22:03:48+00:00

Sudhir Jonathan

2012-10-21T07:27:27+00:00

d981c2a3ecfaf572a836c7533ee3a9553aae327d

Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.

Closes #1401





Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.

Closes #1401







fix(ng-repeat) to work with primitive types
2012-09-11T23:38:42+00:00

Zhenbo Zhang

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

f7a8f17fc72f603de11ca89170bc8d1cad4dae6a












fix(FormController): propagate dirty state to parent forms
2012-09-06T22:54:19+00:00

Kai Groner

2012-06-07T03:23:43+00:00

3d7c752e276f67af6b3bd343babe3606bde1bebe












fix(ngSrc): don't set src if value is empty string
2012-09-06T22:49:49+00:00

Xiangru Chen

2012-07-14T09:40:24+00:00

fd3071843ca53a34a084f5d495f9f0aea82f2ef5

Current implementation of ngSrc may lead to empty src attribute when page is loading.

For example:

<img ng-src="{{image.url}}">
can be temporarily rendered as

<img src="">
before the image resource is loaded.

Some browser emits a request to the current page when seeing <img src=""> (Firefox13 and IE8 will, Chromium20 won't), which leads to performance problems.





Current implementation of ngSrc may lead to empty src attribute when page is loading.

For example:

<img ng-src="{{image.url}}">
can be temporarily rendered as

<img src="">
before the image resource is loaded.

Some browser emits a request to the current page when seeing <img src=""> (Firefox13 and IE8 will, Chromium20 won't), which leads to performance problems.