I turned off compatibility mode, it works better but I’m still having issues. Seems that after a couple of reviews, possibly after I fail an item the queue seems to get stuck.
I see the following in js console:
Uncaught (in promise) TypeError: e.type is undefined
a characters.js:14
listenRenderView reviews.js:204
o application-43559fa94fc26983f5bdf9947044035f960244f4a624a4ef87ba207b93b4fe73.js:5
set application-43559fa94fc26983f5bdf9947044035f960244f4a624a4ef87ba207b93b4fe73.js:5
set jStorageSpy.js:52
randomQuestion reviews.js:155
nextQuestion reviews.js:70
G reviews.js:301
s form.js:116
click_submit Wanikani Double-Check.user.js:859
new_submit_handler Wanikani Double-Check.user.js:719
nrWrapper session:6
I increased my delay settings from 1.5 to 3, and now it seems to not happen any more. Or maybe it’s all random and I’m just getting lucky?
This is one of the scripts I consider essential to making wk good, so I hope it is not breaking.
Oh, I absolutely understand this. And I also see on a re-read how my question could have been misinterpreted. Apologies for that.
What I meant to ask is, given that the Double Check script has to be one of the most used, most referenced userscripts, and given that typos are a thing, and given that it becomes habit to type a word and quickly hit return without double checking that you’ve spelled it correctly, and given that there’s no harm to the educational process if one were to allow a user to undo a mistake such as this, but there is actual harm to a user’s workload from forcing mistakes like this to actually count, has there been given any discussion internally to pull this feature in natively.
e.g. Get rid of the necessity of the userscript entirely by baking its features into vanilla WK.
@Harald1,
Thanks for posting the error message!
The mistake-delay setting probably is just a coincidence, so please post a follow-up if it happens again.
Can you elaborate a little on how you use Mistake Delay?
The Mistake Delay feature itself just keeps you from proceeding for a second or two so you can see what you did wrong. The ability to then change the answer is a separate feature.
For ‘meanings’, WK does have built-in typo forgiveness to an extent, but it doesn’t apply to readings. With Double-Check, do you correct typos on readings? I mean… typos still happen on readings. I know that from experience. But there’s also no good way for WK to do something similar to their typo leniency for readings since (for example) there’s only a single character difference between しょう and しゅう. I know WK has resisted any sort of ability to change answers since it’s easy to abuse. Sort of seems like the responsible users have to suffer for that, though, so I understand both perspectives. Idunno… it’s a dilemma.
That’s exactly it. I get into a rhythm of typing an answer and quickly double tapping return. Especially on a string of correct answers. Then, boom, this habitual behavior would bite when I mistyped a reading kana (which happens quite often). Mistake Delay fixes that by swallowing the habitual second return on incorrect answers.
I agree that WK’s extremely strict behavior for readings is absolutely the correct thing to do. It can not allow misspellings for readings. However it can implement features, like the Mistake Delay feature that I so dearly love, that provides recourse for a human to evaluate whether or not the incorrect answer was due to the human not knowing the answer, or the fingers not responding to the brain correctly.
It’s not an issue when typing in meanings because of WK’s extremely liberal rules on misspelled meanings. In fact I’ll often know I misspelled a meaning and just let it slide because I know what I meant to type and I know WK will accept it. That actually bit me on 示 though. For over a month I thought it was instigate cause WK allows that misspelling. lol.
Talking about strictness of readings, I hope that Okurigana matcher can be integrated. Otherwise, Mark as Wrong button / keyboard shortcut, perhaps.
Mark as Wrong is also helpful for No typo (No Cigar) component. (Then perhaps convert to Right, if necessary. But unlike Anki mode, not immediately Right.)
I want to add to the plea. Having a similar feature natively would be great.
When double check/ignore scripts stop working I stop doing reviews.
I have ADHD, dyslexia and I’m not native English. And my keyboard is glitchy, doesn’t always register, as if I didn’t make enough mistakes on my own
I have so many typos + sometimes can’t recall the correct English word (but know exactly what meaning I want to go for)
It gets so infuriatingly frustrating that I simply give up without an ignore function.
Kitsun and Bunpro both has it as part of their standard, which makes it a lot more stable and predictable.
I hope the changes mentioned includes any form of ignore answer or similar. If not, please consider it.
I didn’t had Double-Check until today due to the recent Wanikani changes and was experiencing the same issue some users had after submitting an answer, you couldn’t proceed with other items in your reviews. My script compatibility option was already off so it wasn’t that. It turned out that I had an old script “Lightning Mode” affecting me (Double-Check already does this). I had to remove that script from violentmonkey. Now things are working fine.
There might be another solution to typo or not, that isn’t native, nor in the script.
How about matching only, like in Anki typing, and not marking as either right or wrong (with Enter delay); then proceed with keyboard shortcut, or Enter. (Maybe simply let “exactly correct” continue without delay as an option.)
Deciding (manually) whether Right or not, can be done with showing multiple keywords / translations, that might may be a part of “warning list”. (Or, also, glosses from Jisho.)
I’m in this same boat. I wont even do any reviews on a machine that doesn’t have Double-Check on it. I need the ability to correct my mistakes because I fat finger so many reviews.
Mine seems to be working after i disabled the script “prioritize overdue reviews” so the best thing to do is disable the scripts one by one until you find the one causing the issue.
There’s something called Lipsurf and you can use it for speech-to-text input to WaniKani. It’s payware, though, but I think you can try it for free. There is a thread for it somewhere in the forums.
I just tried and it doesn’t work sadly. Maybe on pure vocab items, but not kanji. If you use English, it doesn’t hear right and if you use Japanese, it inputs words when you try to do kanji readings. Good idea though!
