From 32b2ae077934dd4349320df08fe66551453c14fd Mon Sep 17 00:00:00 2001
From: cmwelsh <chris@cmwelsh.com>
Date: Tue, 20 Jan 2015 16:23:15 -0500
Subject: [PATCH] Fix error when user clicks a link within 500ms

---
 lib/director/browser.js | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/lib/director/browser.js b/lib/director/browser.js
index 1e47293..16a73b5 100644
--- a/lib/director/browser.js
+++ b/lib/director/browser.js
@@ -55,14 +55,7 @@ var listener = {
       || document.documentMode > 7)) {
       // At least for now HTML5 history is available for 'modern' browsers only
       if (this.history === true) {
-        // There is an old bug in Chrome that causes onpopstate to fire even
-        // upon initial page load. Since the handler is run manually in init(),
-        // this would cause Chrome to run it twise. Currently the only
-        // workaround seems to be to set the handler after the initial page load
-        // http://code.google.com/p/chromium/issues/detail?id=63040
-        setTimeout(function() {
-          window.onpopstate = onchange;
-        }, 500);
+        window.onpopstate = onchange;
       }
       else {
         window.onhashchange = onchange;