angular.js/src/ngScenario, branch v1.2.0-rc.2 feat(scenario): expose jQuery for usage outside of angular scenario 2013-07-31T22:50:12+00:00 Andreas Marek 2013-07-24T19:20:39+00:00 3fdbe81a337c39027929c415e719493755cd8583 The global jQuery reference is removed by angular scenario and only a local scoped reference is kept. To make jQuery available for other code, a new reference angular.scenario.jQuery is added. 
The global jQuery reference is removed by angular scenario and only a local scoped reference is kept. To make jQuery available for other code, a new reference angular.scenario.jQuery is added.
docs(*): fixed typos and ngdoc parameter names 2013-07-27T18:53:41+00:00 Carl Danley 2013-07-22T15:01:00+00:00 258e9862840f9d45709664e0e5b2a18540d8828d 






fix(ngScenario): select().option(val) should prefer exact value match
2013-07-12T09:05:23+00:00

Stephen Merity

2013-06-03T08:09:36+00:00

22a9b1ac07f98d07e1e5d71ce961411b5fa9b42d

With select(...).option(val) it previously would select the first node
which contains the value, even if an exact match was available.
This fix prefers exact matches if available, otherwise it reverts
to the previous 'contains' behaviour for backwards compatibility.

Closes #2856





With select(...).option(val) it previously would select the first node
which contains the value, even if an exact match was available.
This fix prefers exact matches if available, otherwise it reverts
to the previous 'contains' behaviour for backwards compatibility.

Closes #2856







feat(jqLite): switch bind/unbind to more recent jQuery on/off
2013-06-19T19:53:24+00:00

Michał Gołębiowski

2013-06-19T19:52:50+00:00

f1b94b4b599ab701bc75b55bbbbb73c5ef329a93

jQuery switched to a completely new event binding implementation as of
1.7.0, centering around on/off methods instead of previous bind/unbind.
This patch makes jqLite match this implementation while still supporting
previous bind/unbind methods.





jQuery switched to a completely new event binding implementation as of
1.7.0, centering around on/off methods instead of previous bind/unbind.
This patch makes jqLite match this implementation while still supporting
previous bind/unbind methods.







feat(scenario): adds mousedown and mouseup event triggers to scenario
2013-05-14T19:50:36+00:00

Andreas Marek

2013-05-06T08:20:15+00:00

629fb37351ce5778a40a8bc8cd7c1385b382ce75

Added mousedown and mouseup event triggers to scenadio dsl 'element' expression.
Added mousedown and mouseup to the custom jquery trigger method to generate real events.





Added mousedown and mouseup event triggers to scenadio dsl 'element' expression.
Added mousedown and mouseup to the custom jquery trigger method to generate real events.







fix(scenario): update to use our angular-scenario.js rather then karma
2013-05-08T23:40:35+00:00

Misko Hevery

2013-05-08T23:40:00+00:00

29efd39745ac14c89ef8bc79993b51450fd0a8b9












feat($sniffer): Add support for supportsAnimations flag for detecting CSS Animations browser support
2013-05-08T22:40:37+00:00

Matias Niemelä

2013-05-07T14:29:29+00:00

88c3480aff79e1ff5b1ed8bd7f1e05df8ea1e068












test(modules): fix module tests which got disabled by ngMobile
2013-04-18T21:34:53+00:00

Igor Minar

2013-04-18T19:50:49+00:00

5da6b125a7447b4bbabb88b2d82b5634b55c3aea

When ngMobile was merged in, we accidentaly included angular-scenario.js
in the test file set for modules. Loading this file overrode jasmine's
`it` and `describe` global functions which essentially disabled all of
~200 unit tests for wrapped modules.

This change refactors the code to run the wrapped module tests.

I had to extract browserTrigger from scenario runner in order to achieve
this without code duplication.





When ngMobile was merged in, we accidentaly included angular-scenario.js
in the test file set for modules. Loading this file overrode jasmine's
`it` and `describe` global functions which essentially disabled all of
~200 unit tests for wrapped modules.

This change refactors the code to run the wrapped module tests.

I had to extract browserTrigger from scenario runner in order to achieve
this without code duplication.







fix(Scenario): correct bootstrap issue on IE
2013-04-13T07:42:51+00:00

Igor Minar

2013-04-13T06:24:45+00:00

ab755a25f9ca3f3f000623071d8de3ddc4b1d78e

we need to set the deferred bootstrap flag via window.name after the iframe's
src has been set, otherwise IE will reset it to empty string





we need to set the deferred bootstrap flag via window.name after the iframe's
src has been set, otherwise IE will reset it to empty string







feat(Scenario): autodisable animations when running e2e tests
2013-04-04T00:40:15+00:00

Igor Minar

2013-04-03T21:36:57+00:00

fec4ef38815340e8e5a6b65fd6c08f5c74e701d8

animations cause the dom to contain elements that have been removed
from the model but are being animated out.

we could teach the e2e runner to wait for animations but that would
make all tests slower. it should be quite safe to just disable
animations automatically when the app is running via the e2e test
runner.

this change disables only css animations. we should make additional
change that disables js animations as well, but since we don't need
this right now I'm punting on it.





animations cause the dom to contain elements that have been removed
from the model but are being animated out.

we could teach the e2e runner to wait for animations but that would
make all tests slower. it should be quite safe to just disable
animations automatically when the app is running via the e2e test
runner.

this change disables only css animations. we should make additional
change that disables js animations as well, but since we don't need
this right now I'm punting on it.