| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Closes #6207
|
|
Closes #6197
|
|
comment element
This corrects a complicated compiler issue, described in detail below:
Previously, if an element transclusion directive contained an asynchronous directive whose template
contained another element transclusion directive, the inner element transclusion directive would be
linked with the element, rather than the expected comment node.
An example manifestation of this bug would look like so:
```html
<div ng-repeat="i in [1,2,3,4,5]">
<div my-directive>
</div>
</div>
```
`my-directive` would be a replace directive, and its template would contain another element
transclusion directive, like so:
```html
<div ng-if="true">{{i}}</div>
```
ngIf would be linked with this template content, rather than the comment node, and the template element
would be attached to the DOM, rather than the comment. As a result, this caused ng-if to duplicate the
template when its expression evaluated to true.
Closes #6006
Closes #6101
|
|
Closes #6206
|
|
Signed-off-by: Caitlin Potter <caitpotter88@gmail.com>
Closes #6202
|
|
jquery and jqlite
Closes #6159
|
|
|
|
End to end tests will continue to be run on Safari and Firefox on Travis.
Closes #6187
|
|
|
|
|
|
This reverts commit 64d58a5b5292046adf8b28928950858ab3895fcc.
For some weird reason this is causing regressions at Google.
I'm not sure why and I'm running out of time to investigate, so I'm taking
a safe route here and reverting the commit since it's just a refactoring.
|
|
|
|
Use git repo as source and use q-io instead of q-fs
|
|
|
|
Closes #6164
|
|
changed "building and application" to "building an application"
Closes #6156
|
|
$provide misused into $provider
maybe this should be corrected I think
Closes #6146
|
|
We did this due to travis-ci/travis-ci#1293 but since it's possible that this hack is not needed, I'm removing it.
If it turns out that we do need it still then we should ping the travis issue and revert this commit
|
|
test helper code for ngAnimate
Closes #5822
Closes #5917
|
|
The flushNext method of testing is difficult and highly coupled with the behavior
of ngAnimate's $animate workflow. It is much better instead to just queue all
$animate animation calls into a queue collection which is available on the $animate
service when mock.animate is included as a module within test code.
|
|
Closes #6130
|
|
|
|
|
|
Update the Travis and Jenkins configs to run protractor tests on Safari and Firefox as well,
and make the Travis tests run output XML and turn off color.
Fix tests which were failing in Firefox due to clear() not working as expected.
Fix tests which were failing in Safari due to SafariDriver not understanding the minus key,
and disable tests which SafariDriver has no support for.
|
|
point to protractor
|
|
The actual change happened in ng-closure-runner.
The change here just includes the new version.
Closes #4675
|
|
Closes #6124
|
|
Corrects "sortVersionsNatrually" method name in `ngdoc.js` in "sortVersionsNaturally"
|
|
supplied
Closes #6103.
Closed #6099.
|
|
jQuery will construct DOM nodes containing leading whitespace. Prior to this change, jqLite would
throw a nosel minErr due to the first character of the string not being '<'. This change corrects
this behaviour by trimming the element string in jqLite constructor before testing for '<'.
Closes #6053
|
|
WebKit added support for the json responseType value on 09/03/2013
https://bugs.webkit.org/show_bug.cgi?id=73648. Versions of Safari prior to 7 are known to throw when
setting the value "json" as the response type. Other older browsers implementing the responseType.
Other browsers with infrequent update cycles may also be affected.
The json responseType value can be ignored if not supported, because JSON payloads are parsed on the
client-side regardless.
Closes #6115
Closes #6122
|
|
|
|
The version information is now stored only in the tags.
By this we are able to release commits in the past, which
have already been tested, so we don't need a code freeze
or run tests any more. This is also the first step for
letting Travis do the releases in the future.
The package.json now contains the new
property 'branchVersion' that defines which tags are
valid on this branch.
Closes #6116
|
|
"json""
This reverts commit 431bad01835f0294eb159d5b08101d5904828147.
|
|
WebKit added support for the json responseType value on 09/03/2013
https://bugs.webkit.org/show_bug.cgi?id=73648. Versions of Safari prior to 7 are known to throw when
setting the value "json" as the response type. Other older browsers implementing the responseType.
Other browsers with infrequent update cycles may also be affected.
The json responseType value can be ignored if not supported, because JSON payloads are parsed on the
client-side regardless.
Closes #6115
Closes #6122
|
|
change
Add a mention for the slightly breaking change introduced in 1.2.9.
Closes #6022
|
|
requests/responses
ngResource no longer filters properties prefixed with a single "$" character from requests or
responses, correcting a regression introduced in 1.2.6 (cb29632a) which caused shallowCopy and
shallowClearAndCopy to ignore properties prefixed with a single "$".
Closes #5666
Closes #6080
Closes #6033
|
|
"how to" was written twice in a row.
Closes #6110
|
|
"Promises" should be of the possessive form.
Closes #6082
|
|
|
|
the current spec
Currently when a function is injected inside of a test we set the context to undefined which
is a bug.
Closes #6102
|
|
grunt-contrib-jshint into devDependencies
Closes #6085
|
|
Closes #6090
|
|
|
|
|
|
|
|
|
|
|
|
Previously, if a URL parameter value included a $, it would replace the dollar sign with a literal
'$1' for mysterious reasons. Using a function rather than a replacement string circumvents this
behaviour and produces a more expected result.
Closes #6003
Closes #6004
|
