feat(browserTrigger): allow support for custom timeStamps in events

1 files changed, 7 insertions, 2 deletions

diff --git a/src/ngScenario/browserTrigger.js b/src/ngScenario/browserTrigger.js
index 3da6d5ea..c614218d 100644
--- a/src/ngScenario/browserTrigger.js
+++ b/src/ngScenario/browserTrigger.js
@@ -101,7 +101,7 @@
           }
           catch(e) {
             evnt = document.createEvent('TransitionEvent');
-            evnt.initTransitionEvent(eventType, null, null, null, eventData.elapsedTime);
+            evnt.initTransitionEvent(eventType, null, null, null, eventData.elapsedTime || 0);
           }
         }
       }
@@ -116,7 +116,7 @@
           }
           catch(e) {
             evnt = document.createEvent('AnimationEvent');
-            evnt.initAnimationEvent(eventType, null, null, null, eventData.elapsedTime);
+            evnt.initAnimationEvent(eventType, null, null, null, eventData.elapsedTime || 0);
           }
         }
       }
@@ -128,6 +128,11 @@
             pressed('shift'), pressed('meta'), 0, element);
       }
 
+      /* we're unable to change the timeStamp value directly so this
+       * is only here to allow for testing where the timeStamp value is
+       * read */
+      evnt.$manualTimeStamp = eventData.timeStamp;
+
       if(!evnt) return;
 
       var originalPreventDefault = evnt.preventDefault,