angular.js/test, branch v1.0.5 chore(matchers): fix hasBeenCalledOnceWith matcher 2013-02-20T16:44:53+00:00 Igor Minar 2013-02-12T05:24:49+00:00 701d61080a1a5b5084a7fb106086ce6582e16a9e the error message was wrong and misleading 
the error message was wrong and misleading
fix($compile): sanitize values bound to a[href] 2013-02-20T08:40:51+00:00 Igor Minar 2013-02-19T17:55:05+00:00 a8cc4497063118c766bdfa9464c9cbfc59413a81 






fix(ngClass): keep track of old ngClass value manually
2013-02-19T04:35:40+00:00

Per Rovegård

2013-02-15T23:32:38+00:00

2aa212b19c71df82287b4b074da3ab14cbf37348

ngClassWatchAction, when called as a $watch function, gets the wrong old
value after it has been invoked previously due to observation of the
interpolated class attribute. As a result it doesn't remove classes
properly. Keeping track of the old value manually seems to fix this.

Closes #1637





ngClassWatchAction, when called as a $watch function, gets the wrong old
value after it has been invoked previously due to observation of the
interpolated class attribute. As a result it doesn't remove classes
properly. Keeping track of the old value manually seems to fix this.

Closes #1637







fix(compile): should not leak memory when there are top level empty text nodes
2013-02-18T13:04:24+00:00

Pete Bacon Darwin

2013-02-18T12:05:16+00:00

1f23cfe9c751f84d9fc996df6d54961b2e46e868

The change to prevent <span> elements being wrapped around empty text nodes caused these empty text nodes to have scopes and controllers attached, through jqLite.data() calls, which led to memory leaks and errors in IE8.
Now we exclude all but document nodes and elements from having jqLite.data() set both in the compiler and in ng-view.

Fixes: #1968 and #1876





The change to prevent <span> elements being wrapped around empty text nodes caused these empty text nodes to have scopes and controllers attached, through jqLite.data() calls, which led to memory leaks and errors in IE8.
Now we exclude all but document nodes and elements from having jqLite.data() set both in the compiler and in ng-view.

Fixes: #1968 and #1876







fix($httpBackend): patch for Firefox bug w/ CORS and response headers
2013-02-15T00:52:02+00:00

Will Moore

2013-01-18T22:09:19+00:00

0fa8e47fb5d2df5aab820691696f19662669eed0

A workaround for https://bugzilla.mozilla.org/show_bug.cgi?id=608735
In FF getAllResponseHeaders() returns null if the request is the result of CORS.

Tried to format the code so that when a FF patch is released and gains enough
traction it can easily be selected and deleted. Heavily inspired by jQuery's
patch for the same bug. This patch falls short of passing through custom headers
but covers all of the "simple response headers" in the spec at
http://www.w3.org/TR/cors/

This commit should get reverted once Firefox 21 gets out.

Closes #1468

Conflicts:
	src/ng/httpBackend.js





A workaround for https://bugzilla.mozilla.org/show_bug.cgi?id=608735
In FF getAllResponseHeaders() returns null if the request is the result of CORS.

Tried to format the code so that when a FF patch is released and gains enough
traction it can easily be selected and deleted. Heavily inspired by jQuery's
patch for the same bug. This patch falls short of passing through custom headers
but covers all of the "simple response headers" in the spec at
http://www.w3.org/TR/cors/

This commit should get reverted once Firefox 21 gets out.

Closes #1468

Conflicts:
	src/ng/httpBackend.js







fix(a): workaround IE bug affecting mailto urls
2013-02-15T00:43:28+00:00

Igor Minar

2013-02-14T23:13:50+00:00

8043784fd73a4768f4e904fd4121b21cd1fb49b4

Apparently there is a really weird bug in IE6-8 that causes anchor textContent
to be reset with href content when both contain @ symbol.

Inserting a bogus comment node into all anchor elements in IE works around this
browser bug.

I'm fixing the issue via directive because that way we'll fix it for jQuery as
well.

I fixed an e2e test too because it was incorrect.

Closes #1949





Apparently there is a really weird bug in IE6-8 that causes anchor textContent
to be reset with href content when both contain @ symbol.

Inserting a bogus comment node into all anchor elements in IE works around this
browser bug.

I'm fixing the issue via directive because that way we'll fix it for jQuery as
well.

I fixed an e2e test too because it was incorrect.

Closes #1949







fix($rootScope): minor typo fixes
2013-02-14T22:43:32+00:00

Daniel Luz

2012-11-04T21:26:58+00:00

d7e9ae121531f8ad38efaa9c7a20f4b9d70ce15b












fix(compiler): Allow startingTag method to handle text / comment nodes
2013-02-14T22:43:31+00:00

Shyam Seshadri

2013-01-19T04:51:17+00:00

3d0f11212ffcdac060fa4bb990e217e3a0e229fc












fix(resource): Update RegExp to allow urlParams with out leading slash
2013-02-14T22:43:31+00:00

Fredrik Bonander

2013-01-23T09:53:49+00:00

6194e002e2f8860218076a7a5ecf945b0d981843

Will allow reoucese to be loaded from a relative path
Example:
var R = $resource(':path');
R.get({ path : 'data.json' });

Example usage:
Load resources in applications not using webserver, ie local webapp in
on a tablet.





Will allow reoucese to be loaded from a relative path
Example:
var R = $resource(':path');
R.get({ path : 'data.json' });

Example usage:
Load resources in applications not using webserver, ie local webapp in
on a tablet.







fix(numberFilter): fix formatting when "0" passed as fractionSize
2013-02-14T21:46:07+00:00

Kury Kruitbosch

2013-02-11T21:21:15+00:00

75545d4d1c59192d781bb23d8bd2f72c9be37d38

When checking to add decimal and trialing 0s number filter used to check
trueness of fractionSize. "0" evaluating to true causes "123" to return "123."





When checking to add decimal and trialing 0s number filter used to check
trueness of fractionSize. "0" evaluating to true causes "123" to return "123."