I don’t think rfindley has gotten around to fixing this yet so it’s not that it’s back it’s that it is still there.
I’d swear that during a few days it was fixed…
Ok, I think I know why I thought the problem was fixed. I noticed that the “+”/“-” bug only happens in review sessions, not during lessons. The more your know…
Ah, that would be because double-check doesn’t run during lessons. Since there’s no need to undo or change answer.
I finally had a moment to take a look at this. (Well, I should have been doing other things, but I needed a break 
).
Anyway, I’ve posted an update.
1 Like
Thank you so much! It wasn’t my intention to rush you to fix the bug. Still, thank you for your hard work!
Also, the fix works perfectly! 
No worries, I didn’t feel rushed. I enjoy the casual scripting on WK. It feels like a break from the much more difficult stuff I do for work.
I do contract engineering for a living, and I have a ton of work between now and mid-summer, so I’ve been working as many hours as I comfortably can to get ahead. When I say I “should be” doing other things, that’s just my inner taskmaster saying I should maximize productivity. But I wanted a day off, so I took it. 
3 Likes
Having a bit of an issue with the mistake cooldown this past week, it seems to be resetting itself to the default 1.5 seconds very often (sometimes mid-session, but it will always reset when I start a new review session), just wondered if you were aware of this 
Just posting here to make people aware that Double-Check no longer works after the frontend overhaul that launched a few hours ago. I’m not sure if it’s WaniKani Open Framework that broke or if it’s Double-Check itself, but either way it’s very buggy and doesn’t work properly as of now.
No rush to fix it! Just wanted to make it known.
1 Like
For some reason, having the browser debugger open while loading the review page seems to make double check work for me. It does throw an exception about not finding a wanikani controller though
1 Like
Same here, so now I’m using Smouldering Durtles!
Ah, quantum bugs. The best kind.
I’m going to do some totally uninformed and therefore probably wrong speculation that having the debugger pause on the exception is allowing something else to be ready that is more essential to the script functioning.
Tampermonkey can only inject a script when a page is loaded from scratch. Now that the Dashboard uses Turbo (I’m assuming), navigating from the Dashboard to the Reviews page uses Turbo to “inject” the Reviews page rather than actually doing a real page load.
If you go to the Reviews page and click the browser’s Refresh button (not just the refresh hotkey), it forces a fresh load of the Reviews page, which allows Tampermonkey to detect that the Reviews page is loading, and Double-Check should load. (I’m assuming, for now. I don’t have time to investigate until August.)
I’m not sure how the Developer Tools comes into play, but it might be related.
16 Likes
You know, I tried to ‘refresh’ several times in different ways before you posted this and it didn’t work. Hence, I went to Smouldering Durtles. But then I came back and saw your post, followed your directions, and voila! It worked!!! 
So, 私自身, August is just fine for me! Thanks again for ALL you do!
1 Like
Awesome! This fixed it, thank you. Reviews are a lot more stressful and frustrating without your script lol. This saves me some headache.
At least there is a workaround, thanks for telling us!
This workaround seems to work for most (all?) userscripts that work with the review page, for example Jitai.
Thank you, same here, the script does not work unless i hit “refresh” button during Review. Glad there is a workaround.
On Mac CMD+SHIFT+R is a hard refresh in Chromium-based browsers. Worked for me. I think CTRL+SHIFT+R on Windows.
1 Like