(On Chrome, at least,) window.onload() is called once by hand, and once by the browser. This ends up calling setInterval() twice. When stopAnimation() is called later, only the second interval is cleared; so the first one keeps firing forever. Mostly harmless but unnecessary. Only the first hunk of this patch is really needed, but making startAnimation() / stopAnimation() idempotent can't hurt. |
||
---|---|---|
.. | ||
css | ||
html | ||
jpg | ||
js | ||
json | ||
pdf.js | ||
png | ||
favicon.ico | ||
robots.txt |