angular.js/src/ngScenario, branch v1.2.10 fix(input): prevent double $digest when using jQuery trigger. 2013-12-30T23:09:49+00:00 Michał Gołębiowski 2013-12-05T13:59:13+00:00 1147f21999edf9a434cd8d24865a6455e744d858 If an event was performed natively, jQuery sets the isTrigger property. When triggering event manually, the field is not present. Manually triggered events are performed synchronously which causes the "$digest already in progress" error. Closes #5293 
If an event was performed natively, jQuery sets the isTrigger property.
When triggering event manually, the field is not present. Manually
triggered events are performed synchronously which causes the "$digest
already in progress" error.

Closes #5293
chore: update copyright year in file headers 2013-11-22T21:16:23+00:00 Igor Minar 2013-11-22T21:16:23+00:00 bcf12e70e5350595124034c75f6a04e0725205c8 






fix(ngScenario): correctly disable animations for end 2 end tests
2013-11-08T09:03:17+00:00

Pete Bacon Darwin

2013-11-07T11:54:09+00:00

9d0045856351e9db48ddf66f66e210d9cc53d24a












style: make jshint happy
2013-10-22T22:32:41+00:00

Vojta Jina

2013-10-22T21:41:21+00:00

f2fab498303e00d199cb3d19a008670e214d5c10












chore(grunt): add jshint tasks
2013-10-22T22:32:40+00:00

Pete Bacon Darwin

2013-10-21T08:06:53+00:00

934a95d3ef3f72dfc37b0b564624cb4a1286d4f4












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..