| Age | Commit message (Collapse) | Author | 
 | 
Closes #1202
 | 
 | 
This allows common programming patterns to be expressed with more
concise code.
See #1583 for code examples.
 | 
 | 
Today, calling e.g. $http(url, { params: { a: [1,2,3] } }) results in a query
string like "?a=%5B1%2C2%2C3%5D" which is undesirable. This commit enhances
buildURL to createa query string like "?a=1&a=2&a=3".
BREAKING CHANGE: if the server relied on the buggy behavior then either the
backend should be fixed or a simple serialization of the array should be done
on the client before calling the $http service.
Closes #1363
 | 
 | 
Closes #1443
 | 
 | 
Instead of throwning an exception, remove should return undefined when
cache entry to be removed doesn't exist.
Closes #1497
 | 
 | 
Having a $resource defined as:
var R = $resource('/Path', {}, {
  get: {method: 'GET', params: {objId: '1'}},
  perform: {method: 'GET'}
});
was causing both actions to call the same URI (if called in this order):
R.get({}); // => /Path?objId=1
R.perform({}); // => /Path?objId=1
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
window.SecurityPolicy.isActive() is now window.securityPolicy.isActive
since this is available only in Chrome Canary which has already been
updated, we can safely make this change without worrying about
backwards compatilibty.
Closes #1577
 | 
 | 
Under certain circumstances chrome fails to GC scopes
because of buggy optimizations and caching. Nulling out
references to (not from!) other scopes helps Chrome to
realize that this object should be GC-ed.
This is really just a workaround as the real problem needs
to be fixed in Chrome.
See discusstion at:
https://github.com/angular/angular.js/issues/1313#issuecomment-10378451
And chrome bug at:
https://code.google.com/p/v8/issues/detail?id=2073
Closes #1313
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
The cancel function accepts a Promise, but the timeout function
fails to specify returning a Promise.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Per http://www.ietf.org/rfc/rfc3966.txt support tel: links
 | 
 | 
 | 
 | 
 | 
 | 
docs(directive): fix typo
 | 
 | 
Making testacular a dependency to avoid having to install it globally.
(Causes npm issues on some machines)
 | 
 | 
Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.
Closes #1401
 | 
 | 
 | 
 | 
Fix table formatting so headings are bold, rows are separated by lines, and rows have :hover style
 | 
 | 
fixed example app, `simpleAppModule` should have been `myAppModule`.
 | 
 | 
 | 
 | 
Prefixed attributes like data-ng-model and x-ng-model were not being
found by the Selector. It was only looking at ng: and ng- prefixed
attributes.
Added a few tests as well to ensure the aforementioned prefixed
attributes are being matched properly.
Closes #1020
 | 
 | 
 | 
 | 
previously examples like $http where broken because we would strip part of the
filename (http-hello.html -> http)
we really want to strip only the id suffix that we append to disambiguate
common filenames (like index.html) which appear in many examples.
 | 
 | 
Add option to edit source in Angular Docs in Plunkr in addition to JsFiddle
 | 
 | 
Closes #1493
 | 
 | 
if className is undefined or empty string, don't bother looking for directives in there
 | 
 | 
if a node doesn't have children then don't try to compile these non-existent children
 | 
 | 
 | 
 | 
 | 
 | 
This fixes the issue that caused two attr interpolation observers
to be registered for the same attribute as a result of isolate
scope definition with attr (@) property for this attribute.
Duplicate observers would then fight with each other updating the
model.
The issue occured only when this directive was used in a repeater
because that's when we clone the template node which caused the
two observers to point to two different sets of $attr instances.
Closes #1166, #836
 | 
 | 
IEEE 754 floating point sometimes results in values that are very small,
rather than zero. One example is 1.0 + 1.07 - 2.07, which returns
4.440892098500626e-16 instead of 0.
This change tweaks the number formatting logic so that an exponential
value with a negative exponent that is larger than the precision+1
returns 0 instead. For example: with precision 2, anything with an
exponent of -4, -5 or more would become 0. 9e-3 = 0.009 = 0.01, but 9e-4
= 0.0009 = 0.001 = 0.00. This detail is unlikely to matter since this
quirk is usually only triggered with values very close to zero.
Closes #1469
 | 
 | 
Describes several common pitfalls new users of Angular fall into that
I've observed in #angularjs.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
since we don't need the adapter for JsTD (testacular contains its own),
I'm removing this dead code.
 | 
 | 
 | 
 | 
it's bundled with Testacular, so we don't need it here
 | 
 | 
Testacular FTW!
 |