| Age | Commit message (Collapse) | Author |
|
Closes #3943
|
|
The behaviour when null or undefined was passed was not clear.
The exception thrown when source == destination was not documented.
Closes #3946
|
|
Closes #3930
|
|
Closes #3934
|
|
|
|
Firefox 23 has deprecated the use of createEvent for transition and
animation events. We must now use `new TransitionEvent()` and
`new AnimationEvent()` if they are available.
But of course IE doesn't support this format correctly so we must wrap
the attempt in a try block and revert to document.createEvent if necessary..
|
|
onAnimationProgress now checks the event's elapsedTime property before
checking the originalEvent.elapsedTime property.
Use browserTrigger with elapsedTime parameter to trigger animation events
|
|
BREAKING CHANGE: browserTrigger now uses an eventData object instead of direct parameters for mouse events.
To migrate, place the `keys`,`x` and `y` parameters inside of an object and place that as the third parameter
for the browserTrigger function.
|
|
$timeouts to track ongoing animations
Closes #3629
Closes #3874
|
|
Add a summary describing the ignored underscore syntax sugar helper,
with a simple use case example.
Closes #3621
|
|
Closes #3707
|
|
|
|
Closes #3718
|
|
Closes #3724
|
|
I noticed angular was adding these css classes to elements and believe they
should be listed in the documentation at this page. The ng-scope class is
mentioned in the developer guide, hence the link there, and the ng-binding
class is not mentioned anywhere else in the documentation or the guide that
I found.
Closes #3728
|
|
It was not clear what you could pass to specify modules to load in the
`module` parameter of this function. The `modules` parameter takes an
array.
The main case is to provide a String, which is the name of a "predefined"
angular module.
The side cases are to provide a Function (or an annotated function in the
form of an Array), which will be invoked by the injector as a run block.
It is not possible to "define" new modules via this parameter.
Closes #3692
|
|
Clear up confusion about module declaration when using manual bootstrap.
|
|
|
|
Per a request made by Peter Bacon Darwin here: http://www.benlesh.com/2013/02/angular-js-scrolling-to-element-by-id.html?showComment=1370941217879#c8718313084813008967
|
|
Closes #3589
|
|
|
|
|
|
|
|
|
|
|
|
|
|
previously we couldn't use it because of bower bugs
|
|
|
|
behavior
Closes: #3727
|
|
and move animations
Closes #3727
Closes #3603
|
|
cycle is complete
|
|
|
|
example applications
|
|
|
|
Closes #3809
|
|
fix(guide): multiline items in navlist
|
|
|
|
|
|
It's great that IE11 wants to be compatible enough that it doesn't want
to be special cased and treated differently.
However, as long as one has to have a different code path for IE than
for the other supported browsers, we still need to detect and special
case it. For instance, our URL parsing code still needs the same
workaround the we used for IE10. We still see the same Access denied /
TypeError exceptions when setting certain values. FYI, Angular doesn't
generally blindly test for IE – we also check the version number.
Thanks to modern.ie for the free IE11 test VM.
Closes #3682
|
|
|
|
|
|
angular.mocks.$LogProvider $logProvider.debugEnabled(false) is crashing
with undefined when run inside karma/jasmine test runner:
angular.module('foo', []).config(['$logProvider', function ($logProvider) {
$logProvider.debugEnabled(false);
}]);
Closes #3612
|
|
Closes #3341
|
|
|
|
|
|
This is a work-around for Bower/Node.js issue (https://github.com/bower/bower/issues/830). We run `bower install` twice, as the probability of failing twice in a row is very low.
I had to extract `bower` task out of the package, because we need to run `bower install` before building and `grunt bower` can fail, which takes down the whole process and therefore it wouldn't build.
|
|
|
|
|
|
The patch has been released so we don't need to rely on github branch anymore.
|
|
Some browser does not allow to proxy localhost and so SL uses another proxy on the VM. This proxy only proxies some ports (SauceConnect proxies all ports).
This is the issue why Safari didn't connect for e2e tests, because 9877 was not proxied.
This change makes sure we use SL enabled ports.
|