angular.js/test/ng/directive, branch v1.2.0rc1 fix(ngInclude): ensure ngInclude is terminal and uses its own manual transclusion system 2013-08-09T21:39:57+00:00 Matias Niemelä 2013-08-02T21:51:43+00:00 1b5bee4fa12b1f14e117f7ca222c2e2b64cc8558 






docs(compile/selmulti): description for compile/selmulti error
2013-08-09T00:16:46+00:00

Misko Hevery

2013-08-01T22:53:59+00:00

dbd703a9fb864b787bc90c45fd4eb5ded7422f24

Closes #3459





Closes #3459







docs(minErr): rename sce/isecrurl to sce/insecurl
2013-08-08T17:22:32+00:00

Igor Minar

2013-08-08T17:22:32+00:00

0bf0570505e41be266beaa1ccd0266aaed0c3cfb












docs(minerr): fill in error message descriptions
2013-08-08T04:36:59+00:00

Ken Sheedlo

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

e4b6a1eaa4a432b0082c7abbff8f4bb169cf846e

Errors I've documented so far:
- `$injector:cdep`
- `$injector:itkn`
- `$injector:modulerr`
- `$injector:nomod`
- `$injector:pget`
- `$injector:unpr`
- `ng:areq`
- `ng:cpi`
- `ng:cpws`
- `ngModel:noass`

Closes #3430





Errors I've documented so far:
- `$injector:cdep`
- `$injector:itkn`
- `$injector:modulerr`
- `$injector:nomod`
- `$injector:pget`
- `$injector:unpr`
- `ng:areq`
- `ng:cpi`
- `ng:cpws`
- `ngModel:noass`

Closes #3430







feat(ngForm): Supports expression in form names
2013-08-07T20:50:18+00:00

Matthew Windwer

2013-07-02T19:14:24+00:00

8ea802a1d23ad8ecacab892a3a451a308d9c39d7

<form name="ctrl.form"> 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:

<form name="ctrl.form">

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.





<form name="ctrl.form"> 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:

<form name="ctrl.form">

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.







fix(input): fix the email regex to accept TLDs up to 6 characters long
2013-08-07T18:02:44+00:00

neilmcgibbon

2013-08-02T13:57:58+00:00

af731354b0b600f87f15e1573e64a7f7acc70f3d

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).





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).







chore(ngMock): rename $animate.process to $animate.flushNext()
2013-08-03T06:52:37+00:00

Matias Niemelä

2013-07-31T19:38:19+00:00

85d705ab69a89cc5b0c8d2636dede4827d0d8141












fix(isArrayLike) Correctly detect arrayLike items
2013-07-31T18:08:56+00:00

Daniel Herman

2013-07-26T03:15:57+00:00

fad626f3047cd4ff31fe7a4181ca63f275adbae6

Change the implementation of isArrayLike to use one heavily based on the
implementation in jQuery in order to correctly detect array-like
objects, that way functionality like ngRepeat works as expected.





Change the implementation of isArrayLike to use one heavily based on the
implementation in jQuery in order to correctly detect array-like
objects, that way functionality like ngRepeat works as expected.







fix(ngClass): ensure ngClass doesn't fire addClass or removeClass with an empty string
2013-07-30T04:22:05+00:00

Matias Niemelä

2013-07-29T20:24:05+00:00

33d45d8fafb5abf99e6fd811cad1dd57daab918b

If ngClass fires off an add- or removeClass whilst the opposite animation is going on then
the animation will be skipped. The default behavior of ngClass was executing remoteClass
with an empty string while addClass had just fired. This commit fixes that bug.





If ngClass fires off an add- or removeClass whilst the opposite animation is going on then
the animation will be skipped. The default behavior of ngClass was executing remoteClass
with an empty string while addClass had just fired. This commit fixes that bug.







fix(ngInclude): $animate refactoring + use transclusion
2013-07-27T06:49:54+00:00

Matias Niemelä

2013-07-06T04:48:54+00:00

aa2133ad818d2e5c27cbd3933061797096356c8a

BREAKING CHANGE: previously ngInclude only updated its content, after this change
ngInclude will recreate itself every time a new content is included. This ensures
that a single rootElement for all the included contents always exists, which makes
definition of css styles for animations much easier.





BREAKING CHANGE: previously ngInclude only updated its content, after this change
ngInclude will recreate itself every time a new content is included. This ensures
that a single rootElement for all the included contents always exists, which makes
definition of css styles for animations much easier.