angular.js/test, branch v0.10.2 fix(parser): Fix short circuit of logical AND and OR operators 2011-10-07T23:01:09+00:00 Dhruv Manek 2011-09-30T23:55:01+00:00 e1ecc34edd19b95d51fbcb1351b04b9876c974c1 Closes #433 
Closes #433
fix($limitTo): properly handle excessive limits 2011-10-05T18:01:32+00:00 TEHEK Firefox 2011-09-23T18:36:09+00:00 c115fa99240a55e32e1fa39f037056df429be741 `angular.Array.limitTo`'s result should not exceed original input array size Closes #571 
`angular.Array.limitTo`'s  result should not exceed original input array size

Closes #571
fix(jqLite): css should convert dash-separated properties to camelCase 2011-09-28T21:57:00+00:00 Igor Minar 2011-09-27T14:56:54+00:00 ca1e45beafd060b698933886f6425faf365bd31d this fix is needed for Firefox or other browsers that strictly follow dom/css spec which states that element.style should make properties available in camelCased form. Closes #569 
this fix is needed for Firefox or other browsers that strictly follow
dom/css spec which states that element.style should make properties
available in camelCased form.

Closes #569
test(matchers): add toBeOneOf matcher 2011-09-27T19:48:47+00:00 Igor Minar 2011-09-27T18:59:18+00:00 084b83ffa909a2221008acd64fe59b326d30bc87 






fix($resource): action defaults should override resource defaults
2011-09-26T22:44:10+00:00

Marcello Nuccio

2011-09-02T13:50:10+00:00

bf5e5f7bc9ebc7dc6cf8fdf3c4923498b22a8654

defaults definned per action should take precedence over defaults
defined for the whole resource.

This is potentialy a BREAKING CHANGE in case someone relied on the buggy
behavior.





defaults definned per action should take precedence over defaults
defined for the whole resource.

This is potentialy a BREAKING CHANGE in case someone relied on the buggy
behavior.







fix($route): fix regex escaping in route matcher
2011-09-21T11:47:17+00:00

Igor Minar

2011-09-21T11:47:17+00:00

2bc39bb0b4f81b77597bb52f8572d231cf4f83e2












feat(scenarioRunner): adding support for element().prop()
2011-09-16T00:44:34+00:00

Igor Minar

2011-09-15T22:05:13+00:00

6883e8c7a0c121319ced63596718d34e3ab650a8

since jQuery 1.6.4 attr() focuses only on work with element attributes and doesn't deal well with element properties, so adding prop() support is required for getting many e2e tests to pass after upgrading the runner to jQuery 1.6.4.





since jQuery 1.6.4 attr() focuses only on work with element attributes and doesn't deal well with element properties, so adding prop() support is required for getting many e2e tests to pass after upgrading the runner to jQuery 1.6.4.







fix(specs): various fixes to get IE8+jquery unit tests green
2011-09-16T00:44:33+00:00

Igor Minar

2011-09-15T03:36:00+00:00

7ae536d0532b7ad7859f9cf7e47b406f63383f29












fix(specs): fix jQuery to jqLite binding on IE8
2011-09-16T00:44:33+00:00

Igor Minar

2011-09-15T02:54:00+00:00

2170c06924b3a0dc1fef3b383d6a236e670dceea

It appears that this whole time all IE8 unit tests ran only with jqLite. Due to a weird bug in IE[1], we never overwrote jqLite implementation with jQuery, so the tests ran with our jqLite instead.

This affected only IE8 (and likely older) and only in unit testing mode. angular.js - the built artifact binds to jQuery just find.

[1] https://plus.google.com/104744871076396904202/posts/Kqjuj6RSbbT





It appears that this whole time all IE8 unit tests ran only with jqLite. Due to a weird bug in IE[1], we never overwrote jqLite implementation with jQuery, so the tests ran with our jqLite instead.

This affected only IE8 (and likely older) and only in unit testing mode. angular.js - the built artifact binds to jQuery just find.

[1] https://plus.google.com/104744871076396904202/posts/Kqjuj6RSbbT







fix(specs): jQuery now returns attr name instead of true/false for special attrs
2011-09-16T00:44:32+00:00

Igor Minar

2011-09-14T22:47:15+00:00

0e5a24c584d88b17297010676b8e0005b3545efd

for special attrs like 'checked' or 'multiple', jquery now returns the name or undedefined.

e.g. foo.attr('checked') => 'checked' || undefined

The solution is a combination of updating our tests as well as switching
over to prop() instead which properly returns true/false





for special attrs like 'checked' or 'multiple', jquery now returns the name or undedefined.

e.g. foo.attr('checked') => 'checked' || undefined

The solution is a combination of updating our tests as well as switching
over to prop() instead which properly returns true/false