Fix timer not starting bug#53
Conversation
This is working for me in Chrome. I'd like it to work for everyone, but I'd also like to confirm whether this is really a problem before fixing. Could you let me know:
|
|
I had only tested on Windows 10 in Chrome, Edge, Firefox and IE. I only got it to fail in Chrome. And yes, on both the computers that failed I tried clicking on pretty much everything. Nothing worked. On one of the Windows 10 computers that failed I ran When I ran This fixed the problem for me: One last thing to note, offline version worked fine. It didn't work when running from timer.cubing.net but when I forked, cloned, and ran it locally the spacebar began working again. This made it hard for me to test, but I believe the fix should work just fine (except it will allow keys such as Control, Alt, and Shift to start the timer, when they didn't start it before). |
|
I just tried Chrome on 2 more Windows 10 computers and a Windows 8.1 computer. All of them worked. All running Chrome 46.0.2490.86. |
|
I can't reproduce this in Chrome on Windows 10 (in a VM), but
Clicking with the mouse or tapping a keyboard key?
Could you clarify what you mean by this?
Have you tested this? I explicitly make sure that only spacebar starts the timer, and the Ctrl/Alt/Shift don't seem to stop the timer for me (one of my annoyances with qqTimer is that it stops if you switch windows/tabs). |
I tried clicking with the mouse and tabbing around to get the focus on different elements.
Yes, I forked and cloned your repo and ran index.html from the filesystem.
Yes, but I meant to say that these keys would stop the timer, not start. Only spacebar will start the timer. By the way, thank you. The timer works wonderfully now. |
|
Cool, I think things are mostly working as expected; thanks for the fix!
Hmm, I don't think that should make a difference, but I've seen weirder browser behaviour.
Oha, not for me. I'll file a bug for this. |
Spacebar wouldn't start timer in Google Chrome. Only certain keys fire
keypressevent, and different browsers have different standards. All keys firekeydownevent.