<feed xmlns='http://www.w3.org/2005/Atom'>
<title>angular.js/src/ng/directive, branch v1.0.8</title>
<subtitle></subtitle>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/'/>
<entry>
<title>revert: feat(ngForm): Supports expression in form names</title>
<updated>2013-08-22T17:22:17+00:00</updated>
<author>
<name>Igor Minar</name>
</author>
<published>2013-08-22T17:22:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=dbcc44dc80644e4390523ab33204b460f60648ec'/>
<id>dbcc44dc80644e4390523ab33204b460f60648ec</id>
<content type='text'>
This reverts commit 4407e81c618d42c70e8cfca4f52dfc4a669b5c68.

No features or breaking changes in the stable branch please.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 4407e81c618d42c70e8cfca4f52dfc4a669b5c68.

No features or breaking changes in the stable branch please.
</pre>
</div>
</content>
</entry>
<entry>
<title>revert: fix($compile): always instantiate controllers...</title>
<updated>2013-08-21T08:21:02+00:00</updated>
<author>
<name>Igor Minar</name>
</author>
<published>2013-08-21T07:22:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=0d7f19bb620ca4f733e5c202807921501e35172c'/>
<id>0d7f19bb620ca4f733e5c202807921501e35172c</id>
<content type='text'>
fix($compile): always instantiate controllers in parent-&gt;child order

This reverts commit 683fd713c41eaf5da8bfbf53b574e0176c18c518.

It turns out that there is some existing code that relies on the
incorrect timing. Rather than breaking these apps that depend on
stable releases, we are going to keep this changeo only in master
and the apps will need to migrate to the correc timing during the
1.2 upgrade.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
fix($compile): always instantiate controllers in parent-&gt;child order

This reverts commit 683fd713c41eaf5da8bfbf53b574e0176c18c518.

It turns out that there is some existing code that relies on the
incorrect timing. Rather than breaking these apps that depend on
stable releases, we are going to keep this changeo only in master
and the apps will need to migrate to the correc timing during the
1.2 upgrade.
</pre>
</div>
</content>
</entry>
<entry>
<title>docs(input): add missing ngChange directive for email type</title>
<updated>2013-08-13T17:17:44+00:00</updated>
<author>
<name>David Bennett</name>
</author>
<published>2013-05-23T04:27:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=7636670a77c59ee798f3a2adb2a4098483d022ae'/>
<id>7636670a77c59ee798f3a2adb2a4098483d022ae</id>
<content type='text'>
All other input types already have it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
All other input types already have it.
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(ngCloak): hide element even when CSS 'display' is set</title>
<updated>2013-08-12T23:23:38+00:00</updated>
<author>
<name>Vineet Kumar</name>
</author>
<published>2013-06-26T03:37:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=06b0930b6a821bdfed78875f821baf1b8ede2442'/>
<id>06b0930b6a821bdfed78875f821baf1b8ede2442</id>
<content type='text'>
Previously an element like
&lt;div class="foo ng-cloak"&gt;...&lt;/div&gt;
would still be annoyingly visible if it matched a CSS rule like
.foo { display: inline-block; }, overriding ng-cloak's display: none.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously an element like
&lt;div class="foo ng-cloak"&gt;...&lt;/div&gt;
would still be annoyingly visible if it matched a CSS rule like
.foo { display: inline-block; }, overriding ng-cloak's display: none.
</pre>
</div>
</content>
</entry>
<entry>
<title>docs(ngModel): validators should return undefined for invalid values.</title>
<updated>2013-08-09T17:24:48+00:00</updated>
<author>
<name>Niall Smart</name>
</author>
<published>2013-08-09T16:52:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=1dd5d2ec1fee5b19bd93112d640e9c4db09acf97'/>
<id>1dd5d2ec1fee5b19bd93112d640e9c4db09acf97</id>
<content type='text'>
Closes #3525
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Closes #3525
</pre>
</div>
</content>
</entry>
<entry>
<title>docs(ngModel): clarify docs for NgModelController#</title>
<updated>2013-08-09T06:08:08+00:00</updated>
<author>
<name>Igor Minar</name>
</author>
<published>2013-08-09T06:07:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=e290aa8c13205009b763f65a661a7fbcabc867ab'/>
<id>e290aa8c13205009b763f65a661a7fbcabc867ab</id>
<content type='text'>
Closes #3498
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Closes #3498
</pre>
</div>
</content>
</entry>
<entry>
<title>feat(ngForm): Supports expression in form names</title>
<updated>2013-08-07T20:59:41+00:00</updated>
<author>
<name>Matthew Windwer</name>
</author>
<published>2013-07-02T19:14:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=4407e81c618d42c70e8cfca4f52dfc4a669b5c68'/>
<id>4407e81c618d42c70e8cfca4f52dfc4a669b5c68</id>
<content type='text'>
&lt;form name="ctrl.form"&gt; form controller will accessible
as $scope.ctrl.form instead of $scope['ctrl.form']

BREAKING CHANGE:
If you have form names that will evaluate as an expression:

&lt;form name="ctrl.form"&gt;

And if you are accessing the form from your controller:

  Before:

  function($scope) {
    $scope['ctrl.form'] // form controller instance
  }

  After:

  function($scope) {
    $scope.ctrl.form // form controller instance
  }

This makes it possible to access a form from a controller
using the new "controller as" syntax. Supporting the previous
behavior offers no benefit.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
&lt;form name="ctrl.form"&gt; form controller will accessible
as $scope.ctrl.form instead of $scope['ctrl.form']

BREAKING CHANGE:
If you have form names that will evaluate as an expression:

&lt;form name="ctrl.form"&gt;

And if you are accessing the form from your controller:

  Before:

  function($scope) {
    $scope['ctrl.form'] // form controller instance
  }

  After:

  function($scope) {
    $scope.ctrl.form // form controller instance
  }

This makes it possible to access a form from a controller
using the new "controller as" syntax. Supporting the previous
behavior offers no benefit.
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(input): fix the email regex to accept TLDs up to 6 characters long</title>
<updated>2013-08-07T18:18:22+00:00</updated>
<author>
<name>neilmcgibbon</name>
</author>
<published>2013-08-02T13:57:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=ad76e77fce09d0aee28b5ca1a328d5df8596b935'/>
<id>ad76e77fce09d0aee28b5ca1a328d5df8596b935</id>
<content type='text'>
The input field email regex does't not match long domain extensions. This commit extends the email regexp to take a 6 character TLD.

Example 6-character TLDs include .museum and .travel - (e.g. allabout.travel).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The input field email regex does't not match long domain extensions. This commit extends the email regexp to take a 6 character TLD.

Example 6-character TLDs include .museum and .travel - (e.g. allabout.travel).
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(form): pick the right attribute name for ngForm</title>
<updated>2013-07-24T21:41:54+00:00</updated>
<author>
<name>Pawel Kozlowski</name>
</author>
<published>2013-07-18T18:44:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=dc1e55ce1a314b6c1ad4b9d5b4a31226e1fa1e18'/>
<id>dc1e55ce1a314b6c1ad4b9d5b4a31226e1fa1e18</id>
<content type='text'>
Closes #2997
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Closes #2997
</pre>
</div>
</content>
</entry>
<entry>
<title>fix($compile): always instantiate controllers in parent-&gt;child order</title>
<updated>2013-07-22T18:32:50+00:00</updated>
<author>
<name>Igor Minar</name>
</author>
<published>2013-07-18T18:30:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.teddywing.com/fork/angular.js/commit/?id=683fd713c41eaf5da8bfbf53b574e0176c18c518'/>
<id>683fd713c41eaf5da8bfbf53b574e0176c18c518</id>
<content type='text'>
Previously it was possible to get into a situation where child controller
was being instantiated before parent which resulted in an error.

Closes #2738
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously it was possible to get into a situation where child controller
was being instantiated before parent which resulted in an error.

Closes #2738
</pre>
</div>
</content>
</entry>
</feed>
