| Age | Commit message (Collapse) | Author | 
 | 
It seems that docs for these directive were previously hidden by accident
 | 
 | 
aftre -> after
 | 
 | 
Since developers are allowed to customize start/end interpolation
strings, but third-party directive creators don't know about these
customizations, we should standardize on {{ }} in templates of
reusable (third-party) directives. During the compilation, these
templates are then denormalized to use whatever the custom
start/end symbol is, effectively translating the template into the
syntax of the runtime environment.
This addresses an issue raised at http://goo.gl/e8VPV
Existing code should not be affected by this change since project
that do use custom interpolation markers are not expected to use
{{ }} in existing directive templates.
 | 
 | 
 | 
 | 
Closes #1134
 | 
 | 
previously the startSymbol() and endSymbol() getters were exposed only via provider
in the config phase
 | 
 | 
 | 
 | 
I also added missing tests.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Closes #1013
 | 
 | 
previously we expected to find option elements only within select element and if
that was not the case we throw an error. This made it impossible to include datalist
element with nested option elements in the template.
Closes #1165
 | 
 | 
Chrome Canary now has CSP with apis that allow auto-detection. This change
will turn on CSP mode automatically when we detect its presence.
https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html#script-interfaces--experimental
 | 
 | 
Added args in $on() listener syntax declaration
 | 
 | 
this fix ensures that we prevent the default action on form submission
(full page reload) even in cases when the form is being destroyed as
a result of the submit event handler (e.g. when route change is
triggered).
The fix is more complicated than I'd like it to be mainly because
we need to ensure that we don't create circular references between
js closures and dom elements via DOM event handlers that would then
result in a memory leak.
Also the differences between IE8, IE9 and normal browsers make testing
this ugly.
Closes #1238
 | 
 | 
Better than special-casing '$injector' in createInjector.
 | 
 | 
Closes #1075
Closes #1079
Closes #1085
 | 
 | 
When user clicks a link, $location needs to intercept this event.  The <a> doesn't have to be target element of the DOM event, so it needs to traverse the DOM, to find first <a> parent.
If the target element was removed from DOM, during the same event, it would throw an exception. This fixes the issue.
Closes #1058
 | 
 | 
Closes #1051
 | 
 | 
This is a second fix for a regression that was introduced by 92a2e180.
The fix addresses scenarios when the $location service is configured with
a hash prefix.
Closes #1037
 | 
 | 
 | 
 | 
 | 
 | 
This is a fix for a regression that was introduced by 92a2e180
Closes #1037
 | 
 | 
 | 
 | 
we now have two types of namespaces:
- true namespace: angular.* - used for all global apis
- virtual namespace: ng.*, ngMock.*, ... - used for all DI modules
the virual namespaces have services under the second namespace level (e.g. ng.)
and filters and directives prefixed with filter: and directive: respectively
(e.g. ng.filter:orderBy, ng.directive:ngRepeat)
this simplifies urls and makes them a lot shorter while still avoiding name collisions
 | 
 | 
Merging of interpolated class attribute from directive template with replace:true works
Closes #1006
 | 
 | 
This fixes special characters issue with MongoLab.
https://groups.google.com/d/topic/angular/1T6h7bfZ7Rs/discussion
 | 
 | 
Changed the isolate scope binding options to:
  - @attr - attribute binding (including interpolation)
  - =model - by-directional model binding
  - &expr - expression execution binding
This change simplifies the terminology as well as
number of choices available to the developer. It
also supports local name aliasing from the parent.
BREAKING CHANGE: isolate scope bindings definition has changed and
the inject option for the directive controller injection was removed.
To migrate the code follow the example below:
Before:
scope: {
  myAttr: 'attribute',
  myBind: 'bind',
  myExpression: 'expression',
  myEval: 'evaluate',
  myAccessor: 'accessor'
}
After:
scope: {
  myAttr: '@',
  myBind: '@',
  myExpression: '&',
  // myEval - usually not useful, but in cases where the expression is assignable, you can use '='
  myAccessor: '=' // in directive's template change myAccessor() to myAccessor
}
The removed `inject` wasn't generaly useful for directives so there should be no code using it.
 | 
 | 
some browsers (IE) always provide the nodeName as upper-case
 | 
 | 
attr.$observe used to call function only if there was interpolation
on that attribute. We now call the observation function all the time
but we only save the reference to it if interpolation is present.
 | 
 | 
 | 
 | 
This is how it worked in rc9, before refactoring $defer into $timeout.
 | 
 | 
Closes#930
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
This allows location change cancelation
 | 
 | 
 | 
 | 
Publish the application root element as $rootElement
so that it can be injected to other services.
 | 
 | 
templates
BREAKING CHANGE: template in $route definition is now templateUrl
To migrate just rename `template` to `templateUrl`.
 | 
 | 
BREAKING CHANGE
rename $beforeRouteChange to $routeChangeStart
rename $afterRouteChange to $routeChangeSuccess
 | 
 | 
Resolve all promises on route before we fire $afterRouteChange which then renders the ngView.
 | 
 | 
 | 
 | 
JQuery does not catch exceptions either, and just
lets them pass. This allows the exception to be
shown in console.
 | 
 | 
documentation used @return but parser expected
@returns, which made the generated documentation
incomplete.
 |