angular.js/src/ngScenario, branch v1.2.0-rc.3 fix(ngScenario): remove redundant assignment 2013-10-07T18:44:03+00:00 Pete Bacon Darwin 2013-10-07T18:29:10+00:00 a80e96cea184b392505f0a292785a5c66d45e165 Closes #4315 
Closes #4315
feat(browserTrigger): allow support for custom timeStamps in events 2013-09-26T18:19:43+00:00 Matias Niemelä 2013-09-25T04:20:18+00:00 acc2fb84869ac1097434485d56bdc0265120fe34 






fix(ngScenario): fix error message description
2013-09-25T08:46:32+00:00

Pete Bacon Darwin

2013-09-25T08:46:32+00:00

f8f8f754b02459bb789247476cc0da63d2d7370f












fix(scenario): include "not " in error messages if test is inverted
2013-09-18T11:16:42+00:00

Hubert SABLONNIÈRE

2013-09-18T11:14:56+00:00

3589f17824376e9db4e8d002caeb4483943eeb18

Closes #3840





Closes #3840







fix(browserTrigger): do not use document.createEvent method
2013-09-07T06:30:57+00:00

Pete Bacon Darwin

2013-09-07T06:19:25+00:00

4def730de706170995cfb9f62da6397b7cc18285

Firefox 23 has deprecated the use of createEvent for transition and
animation events.  We must now use `new TransitionEvent()` and
`new AnimationEvent()` if they are available.

But of course IE doesn't support this format correctly so we must wrap
the attempt in a try block and revert to document.createEvent if necessary..





Firefox 23 has deprecated the use of createEvent for transition and
animation events.  We must now use `new TransitionEvent()` and
`new AnimationEvent()` if they are available.

But of course IE doesn't support this format correctly so we must wrap
the attempt in a try block and revert to document.createEvent if necessary..







fix(ngScenario): provide event parameters as object
2013-09-06T21:00:37+00:00

Matias Niemelä

2013-09-06T20:06:37+00:00

28f56a383e9d1ff378e3568a3039e941c7ffb1d8

BREAKING CHANGE: browserTrigger now uses an eventData object instead of direct parameters for mouse events.
To migrate, place the `keys`,`x` and `y` parameters inside of an object and place that as the third parameter
for the browserTrigger function.





BREAKING CHANGE: browserTrigger now uses an eventData object instead of direct parameters for mouse events.
To migrate, place the `keys`,`x` and `y` parameters inside of an object and place that as the third parameter
for the browserTrigger function.







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.