| Age | Commit message (Collapse) | Author |
|
Fixes an issue with httpBackend expectations where a given body object
may not match the actual request body if its keys are serialized in a
different order.
Closes #4956
|
|
This is highlighted in angular-phonecat when you try to use the index-async.html
which needs to load the ngResource module asynchronously but fails when it tries
to call `angular.$$minErr` to create the $resourceMinErr object.
Closes #5050
|
|
directives.
Fixes #5069
|
|
directives.
Related to #5069
|
|
Some tests were wrong. However, src/* did not contain problems.
Fixes #5046
|
|
after animation
Closes #4869
|
|
|
|
Keyframe animations trigger on the first CSS class and not the second.
This may cause a slight flicker during a stagger animation since the
animation has already started before the stagger delay is considered.
This fix ensures that the animation is blocked until the active animation
starts which allows for staggering animations to take over properly.
Closes #5018
|
|
operation occurs
Transitions are blocked when the base CSS class is added at the start of the animation. This
causes an issue if the followup CSS class contains animatable-styles. Now, once the animation
active state is triggered (when the animation CSS dom operation occurs) the animation itself
will always trigger an animate without a quick jump.
Closes #5014
Closes #4265
|
|
Closes #4892
|
|
When $compile interpolates a CSS class attribute expression it will
do so by comparing the CSS class value already present on the element.
This may lead to unexpected results when dealing with ngClass values being
added and removed therefore it is best that both compile and ngClass delegate
addClass/removeClass operations to the same block of code.
|
|
Because Grunt was not failing the build, we didn't noticed these failing specs.
|
|
This should be reverted once https://github.com/jasmine-contrib/grunt-jasmine-node/pull/33 gets merged in the upstream repo.
It fixes the problem where Grunt does not fail the build, even though there are failures.
See https://travis-ci.org/angular/angular.js/builds/14329011#L2366
|
|
Closes #5057
|
|
Closes #5058
|
|
Added text from https://github.com/angular/angular.js/issues/4974
Closes #5070
|
|
This changes the priority of ngController to 500 so that it takes precedence
over ngInclude.
Closes #4431, #4521
|
|
on resources.
Previously, calling `MyResource.save(myResourceInstance)`returned
a promise, in contrast to the docs for `$resource`. However,
calling `MyResource.save({name: 'Tobias"})`already correctly
returned a resource instance.
Fixes #4545.
Closes #5061.
|
|
When composing text in CJKV, intermediate buffer for unfinished text should not
be updating the bound scope variables.
Closes #4684
|
|
|
|
The clip property seems to remove the box-shadow property when an absolute
positioned animation is ongoing. This fix changes the property to be border-spacing
which is also very underused. The border-spacing CSS property is only visible
when border-collapse is set to separate.
Closes #4902
Closes #5030
|
|
Also adds `$sniffer.msieDocumentMode` property.
Closes #4931
Closes #5045
|
|
ngClass works by removing all the former classes and then adding all the
new classes to the element during each watch change operation. This may
cause transition animations to never render. The ngClass directive will
now only add and remove the classes that change during each watch operation.
Closes #4960
Closes #4944
|
|
Depending on the animations placed on ngClass, the DOM operation may
run twice causing a race condition between addClass and removeClass.
Depending on what classes are removed and added via $compile this may
cause all CSS classes to be removed accidentally from the element
being animated.
Closes #4949
|
|
In 1.2, the behavior of ngInclude was modified to use DOM APIs rather than jqLite. This means that
even when jQuery was loaded, ngInclude was not calling into it, and thus scripts were not eval'd
as they had been before. Although the use of ngInclude to eval scripts as a lazy-loading strategy
was never an intentional feature, this patch restores the ability to do so.
Closes #3756
|
|
Closes #4953
|
|
Line 162: 'defiend' should be 'defined'
Line 225: 'callback function be excuted' should be 'callback function will be executed'.
Closes #5048
|
|
It was not explicitly and consistently stated that the transient nature of boolean
attributes precludes them from hosting binding expressions.
This change make that more clear and reinforces the simplicity and elegance of the solution.
Closes #5031
|
|
Closes #5029
|
|
Replace "ian" in "in"
Closes #5027
|
|
There should be a space between "braces" and "(`{}`)"
Closes #5026
|
|
The handler is in the controller but was not being used in the template.
Closes #5020
|
|
Closes #5006
|
|
Closes #5005
|
|
Closes #5002
|
|
Closes #4999
|
|
The example code for `$provide.value()` actually used `$provide.constant()`.
It now uses `$provide.value()`.
Closes #4983
Closes #4990
|
|
Closes #4975
|
|
The doc has been modified by the following commit: bcc6e8d4f64a18039e0ed2eee0b54c17471b43e3
But the change was not made for the part of Windows.
Closes #4967
|
|
Closes #4965
|
|
|
|
I still see some disconnection issues with IE9, hopefully this will help a bit.
|
|
|
|
Use different names for the attribute on the element (`info`) and the property (`customerInfo`)
on the isolate scope. Before `customer` was used for both which made it harder to understand.
Closes #4825
|
|
Closes #4719
|
|
The docs did not line up with the codebase / previous steps of the tutorial.
Closes #4988
|
|
Closes #4998
|
|
Closes #4963
|
|
|
|
|