| Age | Commit message (Collapse) | Author |
|
|
|
|
|
Conflicts:
src/ng/animation.js
src/ng/animator.js
src/ng/http.js
|
|
New tests to not call twice a function to get self
|
|
|
|
|
|
|
|
element(selector, label).query(fn) is a very useful function, yet barely
explained. The developer guide should show how this function can be used
to conditionally execute behavior and assertions.
|
|
If a compile function (within a directive) returns a function, it is a
post-link function.
Closes: #2713
|
|
Closes #1316
|
|
|
|
all versioning info is now in package.json and that's where the build scripts read it from
|
|
|
|
Fix a typographical error "it's" -> "its" in the dateFilter
documentation
|
|
"The compilation process happens into two phases." should be "The compilation process happens in two phases."
|
|
|
|
|
|
Because ngDoc generation only takes the last segment of a property name,
each $log.[error|warn|log...].logs property has the same name and is
confusing in the docs.
This commit helps this by adding a link to the $log.* method and also an
appropriate usage example.
|
|
|
|
Matchers are briefly mentioned in the e2e test guide, but there is no
documentation for the available matchers.
|
|
|
|
When you are watching the $location.path(), it has to be wrapped in a
function since it is not attached to the scope and if you pass a string
to $scope.$watch it is evaluated against the $scope.
|
|
The examples in the angular-seed project are better than nothing,
which is what we currently have here!
|
|
Transferred from https://github.com/angular/angular.js/wiki/Using-AngularJS-in-a-Chrome-Extension-environment
|
|
Remove the outdated info in this document related to this API change
https://github.com/angular/angular.js/blob/master/src/ng/rootScope.js#L166
|
|
Added a comma separator in the statement
Removed the word the from the statement
Used whose instead of who's in the following statement
Italicized false in the statement
Used a comma separator in the statement
|
|
With this change, $browser.cookies()["foo"] will behave like
docCookies.getItem("foo") where docCookies is defined at
https://developer.mozilla.org/en-US/docs/DOM/document.cookie
This fixes the issue where, if there's a value for the XSRF-TOKEN cookie
value with the path /, then that value is used for all applications in
the domain even if they set path specific values for XSRF-TOKEN.
Closes #2635
|
|
|
|
|
|
Fix the check for overrides so it is able to handle the empty string
Closes #2575
|
|
|
|
|
|
Closes: #1163
|
|
|
|
|
|
|
|
|
|
|
|
Copying the $$hashKey as part of copy/extend operations makes little
sense since hashkey is used primarily as an object id, especially in
the context of the ngRepeat directive. This change maintains the
existing $$hashKey of an object that is being copied into (likewise for
extend).
It is not uncommon to take an item in a collection, copy it,
and then append it to the collection. By copying the $$hashKey, this
leads to duplicate object errors with the current ngRepeat.
Closes #1875
|
|
closes #1918
|
|
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
|
|
In older Android browsers, `undefined` does not act like `0` in some
arithmetic operations. This leads to dates being formatted with `NaN`
strings in the dateFilter because the implementation of the `dateGetter`
function allows offset to be an optional parameter.
The fix is to convert offset to 0 if it is undefined.
Closes #2277, #2275
|
|
|
|
Before $locationChangeStart event is not broadcast when pressing the back-button on the browser.
Closes #2109
|
|
Closes: #2551
|
|
Specifically adding a directive controller to the example definition
and how to use declare injectables to avoid minification errors.
|
|
|
|
|
|
Fix a context duplication and invocation to a previous context when
doing an access modifier function on the result of a function
Currently, when doing `foo().bar()`, `foo` is called twice, the first
time to get the context and the second one for `bar` to get the
underlying object. Then the call to `bar` is called using the second
instance as self
This is equivalent to doing:
```
var instance1 = foo();
var instance2 = foo();
instance2.bar.apply(instance1);
```
Closes #2496
|
|
|