aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2013-12-05fix($compile): update cloned elements if the template arrives after the cloningTobias Bosch
If an element has a directive whose content is loaded using `templateUrl`, and the element is cloned using a linking function before the template arrives, the clone needs to be updated as well. This also updates `ngIf` and `ngRepeat` to keep the connection to the clone of a tranclude function, so that they know about the changes a directive with `templateUrl` does to the element in the future. Fixes to #4930.
2013-12-05fix(isElement): return boolean value rather than `truthy` value.Caitlin Potter
angular.isElement currently returns a truthy object/function, or false. This patch aims to correct this behaviour by casting the result of the isElement expression to a boolean value via double-negation. Closes #4519 Closes #4534
2013-12-05chore(Angular.js): Use call and === instead of apply and == in type check ↵Karl Seamon
functions Updates isDate et al to use call instead of apply and === instead of ==. The change to call brings minor performance improvement and === is just better practice than ==. http://jsperf.com/call-vs-apply-tostring Closes #5295
2013-12-05chore($resource): Use shallow copy instead of angular.copyKarl Seamon
Replace calls to angular.copy with calls to a new function, shallowClearAndCopy. Add calls to copy for cache access in $http in order to prevent modification of cached data. Results in a measurable improvement to the startup time of complex apps within Google. Closes #5300
2013-12-05chore(Scope): short-circuit after dirty-checking last dirty watcherKarl Seamon
Stop dirty-checking during $digest after the last dirty watcher has been re-checked. This prevents unneeded re-checking of the remaining watchers (They were already checked in the previous iteration), bringing a substantial performance improvement to the average case run time of $digest. Closes #5272 Closes #5287
2013-12-05docs(tutorial/step-6): remove unused `class="diagram"`Andres Kalle
Closes #5197
2013-12-05docs(tutorial/step-3): remember to install karma pluginsPete Bacon Darwin
2013-12-05docs(tutorial/step-2): remember to install karma pluginsPete Bacon Darwin
2013-12-05docs(TRIAGING): Initial doc about triaging issues in AngularTobias Bosch
2013-12-05fix($animate): ensure animations work with directives that share a transclusionMatias Niemelä
Closes #4716 Closes #4871 Closes #5021 Closes #5278
2013-12-04fix(ngInit): evaluate ngInit before ngIncludeCaitlin Potter
The priority of ngInit is adjusted to occur before ngInclude, and after ngController. This enables ngInit to initiallize values in a controller's scope, and also to initiallize values before ngInclude executes. Closes #5167 Closes #5208
2013-12-04chore(travis): move checks from before_scripts to scriptsVojta Jina
If jshint (or any other ci-check) fails, Travis marks the build as "Errored" which I don't think is desider: https://travis-ci.org/angular/angular.js/builds/14938896
2013-12-04fix(input): ensure ngModelWatch() triggers second digest pass when appropriateDaniel Tabuenca
Due to an earlier change, ngModelWatch() no longer returns a value to the caller. This means the digest loop has no way to tell if the watch actually modified anything and so can not schedule another pass. This means any watches that watch form or model controller changes (e.g. watches on form.$valid) that are scheduled prior to an ngModelWatch() will not be able to see any changes made therin. This commit fixes this behavior by returning the latest evaluated ng-model value. Closes #5258 Closes #5282
2013-12-04fix($animate): ensure ms durations are properly roundedMatias Niemelä
Closes #5113 Closes #5162
2013-12-04fix($rootScope): broadcast $destroy event on $rootScopeJeff Cross
Fixes #5169
2013-12-04docs($interpolate): demonstrate a filter in the interpolated expressionSorin Gitlan
Closes #5186
2013-12-04docs(tutorial/step-3): add module to `ng-app` directive in code sampleIwona Lalik
Closes #5184
2013-12-04docs(input): remove deprecated isolated scope pitfallJulien Bouquillon
The 1.2 release fixed the documented pitfall at 909cabd36d779598763cc358979ecd85bb40d4d7 by isolating only the isolated directive's scope. Closes #5179
2013-12-04chore(closure): add `$routeProvider#redirectTo` function parametersDavid Bennett
Closes #5173
2013-12-04docs(tutorial/step-12): fix refernce to incorrect jquery versionElwin Arens
Closes #5156
2013-12-04fix(closure): closure compiler shouldn't rename .defaults.transformRequestMateusz Jedruch
2013-12-04docs(animate.js): fix copy/paste typo in leave docsYves Richard
fix the copy/paste typo within $animate.leave method inside of the $animate docs.
2013-12-04fix($rootScope): clear phase if an exception is raised by a watcherThomas Guillory
Add calls to clearPhase() when an exception is raised by a watcher while a digest cycle, in order to not be stuck on `$digest` scope phase
2013-12-04fix($compile): ensure isolated local watches' lastValue is always in syncDaniel Tabuenca
When using two-way binding with isolate scope, under some circumstances the lastValue variable captured in the parentValueWatch function can get out of sync. Specifically, if both the value in the origin scope as well as the value in the isolate scope get independently updated to the same value within one digest cycle, the lastValue is never updated. This potentially causes the watch to make the wrong decision as to which side to update on subsequent passes. This fixes things by ensuring lastValue is always set to the last seen value even if the watch's logic was short circuited because there was no difference between the values in the original and isolate scopes. Closes #5182
2013-12-03chore(travis): give browsers more time to respondVojta Jina
2013-12-03chore(travis): add IE 11 (SL) to the buildVojta Jina
2013-12-03chore: make it simpler to run tests on SL/BS during local developmentVojta Jina
2013-12-03chore(travis): set SauceLabs build idVojta Jina
2013-12-03chore(travis): disable IE11Vojta Jina
For some reason it's broken on SL.
2013-12-03chore(travis): switch back to SauceLabsVojta Jina
I think we are pretty close to be able to use both. The xhr-polling seems to be pretty stable, but I'm having problems with multiple SSH tunnels (on BS), so let's try to switch back to SL.
2013-12-03chore(travis): define a launcher for IE11 (SauceLabs)Vojta Jina
2013-12-03chore(travis): report both build number and id to BSVojta Jina
2013-12-03chore(travis): log used portsVojta Jina
2013-12-03chore(travis): use different port numbers per buildVojta Jina
We can't establish multiple SSH tunnels for the same port (for BrowserStack). This makes it possible to run multiple parallel builds using BrowserStack.
2013-12-03chore(karma): correct the 404 ignoringVojta Jina
2013-12-03docs: fixed a typo and made a minor edit to docs section of CONTRIBUTING.mdNaomi Black
2013-12-03style(Scope): remove extra wsIgor Minar
2013-12-03style(Scope): rename child scope type from Child to ChildScopeIgor Minar
This change makes it easier to debug angular, especiall when dealing with heap snapshots and hunting for memory leaks.
2013-12-03style(Angular.js): fix typo in commentIgor Minar
2013-12-03fix(ngSanitize): prefer textContent to innerText to avoid layout trashingMichał Gołębiowski
innerText depends on styling as it doesn't display hidden elements. Therefore, it's better to use textContent not to cause unnecessary reflows. However, IE<9 don't support textContent so the innerText fallback is necessary.
2013-12-03chore($parse): micro-optimization for ensureSafeObject functionKarl Seamon
This version matches the "alternate 2.2" version here: http://jsperf.com/ensuresafeobject/2 alternate 2.3 is a bit faster and simpler, but would break backwards compatibility. Closes #5246
2013-12-03fix(jqLite): ignore incompatible nodes on find()Hubert SABLONNIÈRE
When a jqLite collection contains text nodes, find() does not work :-( This fix ignores all nodes than can't do getElementsByTagName() It seems a little bit faster than testing nodeType : http://jsperf.com/nodetype-vs-duck-typing Closes #4120
2013-12-03fix($sanitize): don't rely on YARR regex engine executing immediatelyPete Bacon Darwin
In Safari 7 (and other browsers potentially using the latest YARR JIT library) regular expressions are not always executed immediately that they are called. The regex is only evaluated (lazily) when you first access properties on the `matches` result object returned from the regex call. In the case of `decodeEntities()`, we were updating this returned object, `parts[0] = ''`, before accessing it, `if (parts[2])', and so our change was overwritten by the result of executing the regex. The solution here is not to modify the match result object at all. We only need to make use of the three match results directly in code. Developers should be aware, in the future, when using regex, to read from the result object before making modifications to it. There is no additional test committed here, because when run against Safari 7, this bug caused numerous specs to fail, which are all fixed by this commit. Closes #5193 Closes #5192
2013-12-02chore(travis): increase BrowserStack timeout to 10minVojta Jina
Because IE is retarded.
2013-12-02chore(travis): ignore 404 warnings, debug log into fileVojta Jina
This is a terrible hack/workaround, however I don't think there is any better way to achieve this with log4js.
2013-12-02docs: update CONTRIBUTING.MD with process for doc fixesNaomi Black
2013-12-02chore(travis): fix the build id on browser stackVojta Jina
This just improves the way BrowserStack groups the sessions.
2013-12-02chore: use karma-browserstack-launcher from masterVojta Jina
2013-12-02chore(deps): use regular junit-reporterVojta Jina
We don't need the special branch anymore.
2013-12-02chore(travis): tolerate 2 disconnects to make the build more stableVojta Jina