alrt.io/2minutes50seconds
or alrt.io/2m50s
instead of alrt.io/2%20minutes%2050%20seconds
The %20 makes it really hard to parse.21–30 of 39 posts
alrt.io/2minutes50seconds
or alrt.io/2m50s
instead of alrt.io/2%20minutes%2050%20seconds
The %20 makes it really hard to parse.Just open the JS console and type:
for (var i = 0; i
You will block the JS execution and your next tick will happen when the loop finishes. Using new Date().getTime() should do the job.Edited for formatting.
Simple and cool. How about making the URLs more human readable: alrt.io/2minutes50seconds or alrt.io/2m50s instead of alrt.io/2%20minutes%2050%20seconds The %20 makes it really hard to parse.
alrt.io/2m50s
Still %20s in long format URLs thoughNow, on alert completion do this: window.location.href = 'nyan.cat'; Neat little app, nice to see a simple non-Flash version of http://e.ggtimer.com
The timeLeft -= 1000 approach is not the best one because setTimeout doesn't guarantee when the next tick is gonna happen. Just open the JS console and type: for (var i = 0; i You will block the JS execution and your next tick will happen when the loop finishes. Using new Date().getTime() should do the job. Edited for formatting.
Simple and cool. How about making the URLs more human readable: alrt.io/2minutes50seconds or alrt.io/2m50s instead of alrt.io/2%20minutes%2050%20seconds The %20 makes it really hard to parse.
Not sure if it's updated since you wrote this, but you can do alrt.io/2m50s Still %20s in long format URLs though