<feed xmlns='http://www.w3.org/2005/Atom'>
<title>angular.js/test/ng/directive, branch v1.0.7</title>
<subtitle></subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/'/>
<entry>
<title>fix(ngPluralize): handle the empty string as a valid override</title>
<updated>2013-05-10T19:04:59+00:00</updated>
<author>
<name>Lucas Galfasó</name>
</author>
<published>2013-05-07T12:14:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=42ce8f7f556808da3947aa0bb1c448bbe970bd36'/>
<id>42ce8f7f556808da3947aa0bb1c448bbe970bd36</id>
<content type='text'>
Fix the check for overrides so it is able to handle the empty string

Closes #2575
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix the check for overrides so it is able to handle the empty string

Closes #2575
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(select): ensure empty option is not lost in IE9</title>
<updated>2013-05-07T20:29:44+00:00</updated>
<author>
<name>Chad Smith</name>
</author>
<published>2013-03-19T10:22:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=f1a34f0908cf3629da4f97b20d0c77e315e93cb5'/>
<id>f1a34f0908cf3629da4f97b20d0c77e315e93cb5</id>
<content type='text'>
Fix a check inside render for select elements with ngOptions, which
compares the selected property of an element with it's desired state.
Ensure the placeholder, if available, is explicitly selected if the model
value can not be found in the option list.
Without these fixes it's up to the browser implementation to decide which
option to choose. In most browsers, this has the effect of displaying the
first item in the list. In IE9 however, this causes the select to display
nothing.

Closes #2150, #1826
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fix a check inside render for select elements with ngOptions, which
compares the selected property of an element with it's desired state.
Ensure the placeholder, if available, is explicitly selected if the model
value can not be found in the option list.
Without these fixes it's up to the browser implementation to decide which
option to choose. In most browsers, this has the effect of displaying the
first item in the list. In IE9 however, this causes the select to display
nothing.

Closes #2150, #1826
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngModel): use paste/cut events in IE to support context menu</title>
<updated>2013-04-17T20:50:07+00:00</updated>
<author>
<name>Mark Dalgleish</name>
</author>
<published>2013-03-21T07:07:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=3ebc2c2442755aa93a908b0ee9e372c8e6e4a924'/>
<id>3ebc2c2442755aa93a908b0ee9e372c8e6e4a924</id>
<content type='text'>
In IE the model is not updated when the input value is modified using the context
menu, e.g. pasting from the clipboard, or cutting all or part of the current value.
To capture these changes, we bind to the proprietary 'paste' and 'cut' events.

Closes #1462
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In IE the model is not updated when the input value is modified using the context
menu, e.g. pasting from the clipboard, or cutting all or part of the current value.
To capture these changes, we bind to the proprietary 'paste' and 'cut' events.

Closes #1462
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngClass): should remove classes when object is the same but property has changed</title>
<updated>2013-04-16T12:22:37+00:00</updated>
<author>
<name>Pete Bacon Darwin</name>
</author>
<published>2013-04-16T11:29:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=7898490779c2b2c359f1887c723ee260b3865639'/>
<id>7898490779c2b2c359f1887c723ee260b3865639</id>
<content type='text'>
If you wire up ngClass directly to an object on the scope, e.g. ng-class="myClasses",
where scope.myClasses = { 'classA': true, 'classB': false },
there was a bug that changing scope.myClasses.classA = false, was not being picked
up and classA was not being removed from the element's CSS classes.

This fix uses angular.equals for the comparison and ensures that oldVal is a copy of
(rather than a reference to) the newVal.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If you wire up ngClass directly to an object on the scope, e.g. ng-class="myClasses",
where scope.myClasses = { 'classA': true, 'classB': false },
there was a bug that changing scope.myClasses.classA = false, was not being picked
up and classA was not being removed from the element's CSS classes.

This fix uses angular.equals for the comparison and ensures that oldVal is a copy of
(rather than a reference to) the newVal.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix failing test in IE 10</title>
<updated>2013-03-15T05:04:06+00:00</updated>
<author>
<name>Shyam Seshadri</name>
</author>
<published>2013-03-14T16:42:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=654dd1d5e8c7612f61678e968d0864a3d04082be'/>
<id>654dd1d5e8c7612f61678e968d0864a3d04082be</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngClass): keep track of old ngClass value manually</title>
<updated>2013-02-19T04:35:40+00:00</updated>
<author>
<name>Per Rovegård</name>
</author>
<published>2013-02-15T23:32:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=2aa212b19c71df82287b4b074da3ab14cbf37348'/>
<id>2aa212b19c71df82287b4b074da3ab14cbf37348</id>
<content type='text'>
ngClassWatchAction, when called as a $watch function, gets the wrong old
value after it has been invoked previously due to observation of the
interpolated class attribute. As a result it doesn't remove classes
properly. Keeping track of the old value manually seems to fix this.

Closes #1637
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ngClassWatchAction, when called as a $watch function, gets the wrong old
value after it has been invoked previously due to observation of the
interpolated class attribute. As a result it doesn't remove classes
properly. Keeping track of the old value manually seems to fix this.

Closes #1637
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(compile): should not leak memory when there are top level empty text nodes</title>
<updated>2013-02-18T13:04:24+00:00</updated>
<author>
<name>Pete Bacon Darwin</name>
</author>
<published>2013-02-18T12:05:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=1f23cfe9c751f84d9fc996df6d54961b2e46e868'/>
<id>1f23cfe9c751f84d9fc996df6d54961b2e46e868</id>
<content type='text'>
The change to prevent &lt;span&gt; elements being wrapped around empty text nodes caused these empty text nodes to have scopes and controllers attached, through jqLite.data() calls, which led to memory leaks and errors in IE8.
Now we exclude all but document nodes and elements from having jqLite.data() set both in the compiler and in ng-view.

Fixes: #1968 and #1876
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The change to prevent &lt;span&gt; elements being wrapped around empty text nodes caused these empty text nodes to have scopes and controllers attached, through jqLite.data() calls, which led to memory leaks and errors in IE8.
Now we exclude all but document nodes and elements from having jqLite.data() set both in the compiler and in ng-view.

Fixes: #1968 and #1876
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(a): workaround IE bug affecting mailto urls</title>
<updated>2013-02-15T00:43:28+00:00</updated>
<author>
<name>Igor Minar</name>
</author>
<published>2013-02-14T23:13:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=8043784fd73a4768f4e904fd4121b21cd1fb49b4'/>
<id>8043784fd73a4768f4e904fd4121b21cd1fb49b4</id>
<content type='text'>
Apparently there is a really weird bug in IE6-8 that causes anchor textContent
to be reset with href content when both contain @ symbol.

Inserting a bogus comment node into all anchor elements in IE works around this
browser bug.

I'm fixing the issue via directive because that way we'll fix it for jQuery as
well.

I fixed an e2e test too because it was incorrect.

Closes #1949
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Apparently there is a really weird bug in IE6-8 that causes anchor textContent
to be reset with href content when both contain @ symbol.

Inserting a bogus comment node into all anchor elements in IE works around this
browser bug.

I'm fixing the issue via directive because that way we'll fix it for jQuery as
well.

I fixed an e2e test too because it was incorrect.

Closes #1949
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngSwitch): don't leak when destroyed while not attached</title>
<updated>2013-01-18T08:03:42+00:00</updated>
<author>
<name>danilsomsikov</name>
</author>
<published>2013-01-11T17:21:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=89303fd2dccb780bea594b16b8ec85d9f3bd8f92'/>
<id>89303fd2dccb780bea594b16b8ec85d9f3bd8f92</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngRepeat): correctly apply $last if repeating over object</title>
<updated>2013-01-17T08:25:07+00:00</updated>
<author>
<name>Pete Bacon Darwin</name>
</author>
<published>2013-01-11T12:47:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=ed2fd2d0caad4e4b45f79bb39fd2a8b03fea8faa'/>
<id>ed2fd2d0caad4e4b45f79bb39fd2a8b03fea8faa</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
</feed>
