angular.js/src/ng, branch v1.2.0-rc.3 docs: add missing priority documentation for structural directives 2013-10-14T16:53:32+00:00 Igor Minar 2013-10-14T16:53:32+00:00 08cdd77c28e95cb2d01d568f31873124c97ec33a 






docs(ngInit): fix typo
2013-10-14T06:40:57+00:00

Tyler McGinnis

2013-10-11T22:59:08+00:00

a780df877935f350990826bc5e577afa2b460006

Closes #4384





Closes #4384







docs(ngNonBindable): improve description
2013-10-14T06:20:31+00:00

Pete Bacon Darwin

2013-10-12T22:38:27+00:00

977b482b0b9ee41fee7feb8d1016f3d86f54abc7

Closes #4391





Closes #4391







docs(booleanAttrs): improve grammar and clarity
2013-10-14T06:12:20+00:00

Dave Peticolas

2013-10-13T00:33:45+00:00

e79a20e1ca2e725100acedc0ba5ac014fea0f412

Closes #4392





Closes #4392







fix($compile): abort compilation when duplicate element transclusion
2013-10-12T00:12:24+00:00

Igor Minar

2013-10-11T04:35:54+00:00

63c5334c84b7269428c710226764d1f08a36e0d4

Issue an error and abort compilation when two directives that ask for transclusion are found
on a single element. This configuration is not supported and we previously failed to issue
the error because in the case of element transclusion the compilation is re-started and this
caused the compilation context to be lost.

The ngRepeat directive has been special-cased to bypass this warning because it knows how to
handle this scenario internally.

This is not an ideal solution to the problem of multiple transclusions per element, we are
hoping to have this configuration supported by the compiler in the future. See #4357.

Closes #3893
Closes #4217
Closes #3307





Issue an error and abort compilation when two directives that ask for transclusion are found
on a single element. This configuration is not supported and we previously failed to issue
the error because in the case of element transclusion the compilation is re-started and this
caused the compilation context to be lost.

The ngRepeat directive has been special-cased to bypass this warning because it knows how to
handle this scenario internally.

This is not an ideal solution to the problem of multiple transclusions per element, we are
hoping to have this configuration supported by the compiler in the future. See #4357.

Closes #3893
Closes #4217
Closes #3307







fix(directives): correct priority of structural directives
2013-10-12T00:12:24+00:00

Igor Minar

2013-10-11T19:58:57+00:00

b7af76b4c5aa77648cc1bfd49935b48583419023

BREAKING CHANGE: the priority of ngRepeat, ngSwitchWhen, ngIf,
ngInclude and ngView has changed. This could affect directives that
explicitly specify their priority.

In order to make ngRepeat, ngSwitchWhen, ngIf, ngInclude and ngView
work together in all common scenarios their directives are being
adjusted to achieve the following precendence:

Directive        | Old Priority | New Priority
=============================================
ngRepeat         | 1000         | 1000
---------------------------------------------
ngSwitchWhen     | 500          | 800
---------------------------------------------
ngIf             | 1000         | 600
---------------------------------------------
ngInclude/ngView | 1000         | 400





BREAKING CHANGE: the priority of ngRepeat, ngSwitchWhen, ngIf,
ngInclude and ngView has changed. This could affect directives that
explicitly specify their priority.

In order to make ngRepeat, ngSwitchWhen, ngIf, ngInclude and ngView
work together in all common scenarios their directives are being
adjusted to achieve the following precendence:

Directive        | Old Priority | New Priority
=============================================
ngRepeat         | 1000         | 1000
---------------------------------------------
ngSwitchWhen     | 500          | 800
---------------------------------------------
ngIf             | 1000         | 600
---------------------------------------------
ngInclude/ngView | 1000         | 400







fix($compile): make order directives w/ same priority deterministic
2013-10-12T00:12:24+00:00

Igor Minar

2013-10-11T23:46:32+00:00

4357da857587d3c28790e7dc654664bec5808768

Array.prototype.sort is speced out to be as potentionally unstable sort,
which is how it's implemented in FF and IE. This has caused the order
of directives with the same priority to vary between browsers.

For consistency sake, we now consider directive name and registration,
order when determining the order of directives with the same priority.

Note: it is still possible to get into a situation when the directive
order is underministic - when source files are loaded asynchronously
in non-deterministic order and there are are directives registered
with the same name and priority, the order in which they will be applied
will depend on the file load order.





Array.prototype.sort is speced out to be as potentionally unstable sort,
which is how it's implemented in FF and IE. This has caused the order
of directives with the same priority to vary between browsers.

For consistency sake, we now consider directive name and registration,
order when determining the order of directives with the same priority.

Note: it is still possible to get into a situation when the directive
order is underministic - when source files are loaded asynchronously
in non-deterministic order and there are are directives registered
with the same name and priority, the order in which they will be applied
will depend on the file load order.







style: strip white space from files
2013-10-12T00:12:24+00:00

Igor Minar

2013-10-11T19:21:34+00:00

83fbaa54f13ff94d193115de0eaa3799739af3a5












chore($compile): remove dead code
2013-10-12T00:12:23+00:00

Igor Minar

2013-10-10T22:45:41+00:00

9f4d99f4eaa53ea4b186a2954b23ce4c86643947












docs(ngAnimate): fix typos
2013-10-11T12:34:00+00:00

Hack Reactor Students

2013-10-11T00:23:08+00:00

3205166d80da268ac66768496f0bc1d956aa0f77

Closes #4375





Closes #4375