angular.js/test, branch v1.0.0rc10 fix($rootScope): TTL exception does not clear $$phase 2012-05-23T23:01:20+00:00 Misko Hevery 2012-05-23T21:49:01+00:00 989446eceee697b15ecb5df1f491dfbcff352256 When $digest() throws infinite digest exception it does not properly clear the $phase leaving the scope in an inconsistent state. Closes #979 
When $digest() throws infinite digest exception it
does not properly clear the $phase leaving the scope
in an inconsistent state.

Closes #979
 feat($timeout): add $timeout service that supersedes $defer 2012-05-23T22:00:56+00:00 Igor Minar 2012-05-23T06:05:26+00:00 4511d39cc748288df70bdc258f98a8f36652e683 $timeout has a better name ($defer got often confused with something related to $q) and is actually promise based with cancelation support. With this commit the $defer service is deprecated and will be removed before 1.0. Closes #704, #532 
$timeout has a better name ($defer got often confused with something related to $q) and
is actually promise based with cancelation support.

With this commit the $defer service is deprecated and will be removed before 1.0.

Closes #704, #532
fix(ngRepeat): expose $first, $middle and $last instead of $position 2012-05-22T21:18:15+00:00 Max 2012-05-02T16:51:31+00:00 1d388676e3b97b6171fc498e82545bd437ee6fd1 $position marker doesn't work well in cases when we have just one item in the list because then the item is both the first and last. To solve this properly we need to expose individual $first and $middle and $last flags. BREAKING CHANGE: $position is not exposed in repeater scopes any more To update, search for $position and replace it with one of $first, $middle or $last. Closes #912 
$position marker doesn't work well in cases when we have just one item
in the list because then the item is both the first and last. To solve
this properly we need to expose individual $first and $middle and $last
flags.

BREAKING CHANGE: $position is not exposed in repeater scopes any more

To update, search for $position and replace it with one of $first,
$middle or $last.

Closes #912
feat(scope): add event.preventDefault() and event.defaultPrevented 2012-05-17T22:47:53+00:00 Vojta Jina 2012-04-27T15:31:11+00:00 84542d2431d20de42d6ec27c9d3435dd72dbe2ee 






refactor(scope.$emit): rename event.cancel() to event.stopPropagation()
2012-05-17T22:47:52+00:00

Vojta Jina

2012-04-27T11:14:46+00:00

91db99208e197a73584a88a8d835eeb55c466335

Breaks event.cancel() is event.stopPropagation()





Breaks event.cancel() is event.stopPropagation()







fix(jqLite): have same expando format as jQuery
2012-05-17T17:36:45+00:00

Misko Hevery

2012-05-09T23:27:15+00:00

acf095d1783e30e750d046ef24e81b5a0a31fbd4












fix(jqLite): .data()/.bind() memory leak
2012-05-15T04:56:22+00:00

Misko Hevery

2012-05-09T23:27:15+00:00

ec1c5dfaee32f9638cedd28bb96bbbecce9d0cf0

Since angular attaches scope/injector/controller
into DOM it should clean up after itself. No need
to complain about memory leaks, since they can
only happened on detached DOM. Detached DOM would
only be in tests, since in production the DOM
would be attached to render tree and removal
would automatically clear memory.





Since angular attaches scope/injector/controller
into DOM it should clean up after itself. No need
to complain about memory leaks, since they can
only happened on detached DOM. Detached DOM would
only be in tests, since in production the DOM
would be attached to render tree and removal
would automatically clear memory.







fix($sniffer): report history false on Android < 4
2012-05-14T22:12:51+00:00

Vojta Jina

2012-05-14T21:14:52+00:00

7b739c97028be2a5d5aef679ef1f8064cd10d386

Android has history.pushState, but it does not update the location correctly:
http://code.google.com/p/android/issues/detail?id=17471

Closes #904





Android has history.pushState, but it does not update the location correctly:
http://code.google.com/p/android/issues/detail?id=17471

Closes #904







fix($location): support urls with any protocol
2012-05-14T21:45:56+00:00

Igor Minar

2012-05-12T06:56:37+00:00

c1533ef5762199bea18d3bf3bcba7fcf89272931

The url used for location parsing was quite strict and did not support
custom url schemes like "chrome-extension://". With this change the only
requirement for scheme is that it doesn't contain ":" character.





The url used for location parsing was quite strict and did not support
custom url schemes like "chrome-extension://". With this change the only
requirement for scheme is that it doesn't contain ":" character.







fix($browser/$location): single quote in url causes infinite digest in FF
2012-05-14T04:53:19+00:00

Igor Minar

2012-05-14T04:53:19+00:00

679cb8a74a684454fe38fa9e1ddad396bb598c52

The real issue is in FF, see https://bugzilla.mozilla.org/show_bug.cgi?id=407172.

FF overly encodes stuff which breaks our expectations and then we fail .url() != currentUrl.absUrl()
comparison unexpectidly, which leads to infinite digest.

The workaround is to correct for this inconsistency in $browser and decode any single quotes in urls.

Closes #920





The real issue is in FF, see https://bugzilla.mozilla.org/show_bug.cgi?id=407172.

FF overly encodes stuff which breaks our expectations and then we fail .url() != currentUrl.absUrl()
comparison unexpectidly, which leads to infinite digest.

The workaround is to correct for this inconsistency in $browser and decode any single quotes in urls.

Closes #920