The overall approach varies based on your Jasmine version. Jasmine 1.3 You can use waitsFor: it( “Disable all submit buttons”, function() { // Get a button var $button = $( ‘#ai1ec_subscribe_users’ ); // Call the function utility_functions.block_all_submit_and_ajax( $button.get(0) ); // Wait 100ms for all elements to be disabled. waitsFor(‘button to be disabled’, function(){ var found … Read more
Maybe you should use setInterval()
According to the MDN reference, the specification requires that there is a minimum timeout. If you provide something less than this (HTML5 spec says 4ms) then the browser will just ignore your delay and use the minimum. So negatives should be fine, since it’ll just be less than the minimum. Apparently, this isn’t always the … Read more
A few useful facts might help clarify what’s happening: JavaScript is single-threaded. Asynchronous callbacks are assigned to a message placed in a message queue. When no code is currently executing, the event loop polls the message queue, requesting the next message in line to be processed (executed). setTimeout adds a message (with the callback provided) … Read more
Is the code contained in a function? function test() { setTimeout(…); // code that you cannot modify? } In that case, you could prevent the function from further execution, and then run it again: function test(flag) { if(!flag) { setTimeout(function() { alert(); test(true); }, 5000); return; } // code that you cannot modify }
You could do one of two things: 1: Actually wait in the test 250+1 ms in a setTimeout(), then check if the element actually disappeared. 2: use fakeAsync() and tick() to simulate time in the test – a tick() will resolve the setTimeout in the original close(), and the check could happen right after in … Read more
Native JavaScript promises don’t have any timeout mechanism. The question about your implementation would probably be a better fit for http://codereview.stackexchange.com, but a couple of notes: You don’t provide a means of actually doing anything in the promise, and There’s no need for clearTimeout within your setTimeout callback, since setTimeout schedules a one-off timer. Since … Read more
You have a choice of with or without webWorkers: Without WebWorkers For code that needs to interact with the DOM or with lots of other state in your app, you can’t use a webWorker so the usual solution is to break your work into chunks do each chunk of work on a timer. The break … Read more
Classic javascript mistake. setTimeout(function(){this.setState({timePassed: true})}, 1000) When setTimeout runs this.setState, this is no longer CowtanApp, but window. If you define the function with the => notation, es6 will auto-bind this. setTimeout(() => {this.setState({timePassed: true})}, 1000) Alternatively, you could use a let that = this; at the top of your render, then switch your references to … Read more
What I do is: var timer = null; if (timer != null) { window.clearTimeout(timer); timer = null; } else { timer = window.setTimeout(yourFunction, 0); }