| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
Duplicate 'that' words present in the document, just remove one of them.
Closes #6469
|
|
|
|
- add a link to a tutorial on intergrating angular and django
|
|
Mention common cause of error is binding to a new array on every $digest loop.
Closes #6465
|
|
- add missing 'C' restriction for class names
|
|
- add linked list to top of document
- add anchor elements to secondary headings
closes #6287
|
|
Closes #6403
|
|
|
|
Transitions must be blocked so that the initial CSS class can be applied
without triggering an animation. Keyframes do not need to be blocked since
animations are always triggered on the starting CSS class, however, if a
stagger animation is set to occur then all elements for index > 0 should
be blocked. This is to prevent the animation from occuring early on before
the stagger delay for the given element has passed.
With ngAnimate and keyframe animations, IE10 and Safari will render a slight
flicker effect caused by the blocking. This fix resolves this issue.
Closes #4225
|
|
cancelChildAnimations
When an element containing both ng-repeat and ng-if directives attempts to remove any items from
the repeat collection, the following error is thrown: "TypeError Cannot call method 'querySelectorAll'
of undefined". This happens because the cancelChildAnimations code naively belives that the jqLite
object always has an element node within it. The fix in this commit addresses to securely check to see
if a node was properly extracted before any child elements are inspected.
Closes #6205
|
|
animations
If enter -> leave -> enter -> leave occurs then the first leave animation will
animate alongside the second. This causes the very first DOM node (the view in ngView
for example) to animate at the same time as the most recent DOM node which ends
up being an undesired effect. This fix takes care of this issue.
Closes #5886
|
|
|
|
closing timeout
Closes #6395
|
|
These errors in the docs were preventing some parts of the docs from being
parsed.
|
|
|
|
This reverts commit cad717b1171affc3d540cea372576c70b0cb2295.
This change causes regressions in existing code and after closer inspection
I realized that it is trying to fix an issue that is should not be considered
a valid issue.
The location service was designed to work against either "hash" part of the
window.location when in the hashbang mode or full url when in the html5 mode.
This change tries to merge the two modes partially, which is not right. One
reason for this is that the search part of window.location can't be modified
while in the hashbang mode (a browser limitation), so with this change part
of the search object should be immutable and read-only which will only cause
more confusion.
Relates to #5964
|
|
Per ECMAScript 5.1 specification trailing commas are allowed in object and
array literals. All modern browsers as well as IE>8 support this syntax.
This commit adds support for such syntax to Angular expressions.
|
|
|
|
Fixed a mistake, changed invoice to invoice2.
Closes #6438
|
|
|
|
|
|
|
|
Closes #6418
|
|
Closes #5755
|
|
Closes #6415
|
|
use of the article, both definite and indefinite, is not optional
Closes #5981
|
|
Closes #6241
|
|
Closes #6408
|
|
`{jQuery/jqLite element}` is not a valid jsdoc type and breaks when being
parsed causing the documentation to look wrong. This commit changes all
such param tags to use `DOMElement` instead, which is what is used for
similar params in `$compile` and `angular.element`.
|
|
Closes #6406
|
|
Currently there is only a minimal test spec in place. But this will now
be run as part of the test tasks.
|
|
Before we were simply sending the current location, but multiple URLs map
to the same document.
Now, we use the canonical path of the current document if available and
fall back to the $location path otherwise.
Includes tests!!
Closes #6402
|
|
Fixes #6193
Closes #6226
|
|
browser
Use the multiConfiguration ability of Protractor to start tests on multiple browsers
from the same travis cell. Group tests by type (jquery, jqlite, or docs tests) instead
of by browser. Turn on tests for jQuery.
|
|
Apparently some example files were referenced in angularFiles.js, and this was missed when
2f4513339337bb8aa6c9dfe1191d169b4fc57999 was checked in. This cleans it up.
Closes #6405
|
|
Before this fix, search queries in hashbang mode were ignored if the hash was not present in the
url. This patch corrects this by ensuring that the search query is available to be parsed by
urlResolve when the hashbang is not present.
Closes #5964
|
|
In browsers where HTML5 constraint validation is (partially) implemented, an invalid number
entered into an input[type=number] (for example) input element would be visible to the
script context as the empty string. When the required or ngRequired attributes are not used,
this results in the invalid state of the input being ignored and considered valid.
To address this, a validator which considers the state of the HTML5 ValidityState object is
used when available.
Closes #4293
Closes #2144
Closes #4857
Closes #5120
Closes #4945
Closes #5500
Closes #5944
|
|
Complimentary change to match changed $parse behaviour.
|
|
There are always going to be false positives here, unfortunately. But
testing different properties will hopefully reduce the number of false
positives in a meaningful way, without harming performance too much.
Closes #4805
Closes #5675
|
|
This change makes the ngHref directive useful for SVGAElements by having it bind
to the xlink:href attribute rather than the href attribute.
Closes #5904
|
|
Closes #6342
|
|
Fixes #5985
Closes #6401
|
|
Let these poor scripts retire, goodness.
Closes #6398
Closes #3310
|
|
|