This is a game changer. Thank you!!
1 Like
Would you consider adding an optional delay in how long it takes to process the answer. I’d personally prefer it had a delay of 300-500ms such that I can type the full answer i think it is
The issue arrises in cases such as I believe the answer is
ばんごう
but as i type the answer it auto commits once i have typed past this one:
ばんご
Would be good to add a delay of 500ms or make it customisable for those that type slower maybe such that we can type past the correct answer without it being auto commited
OR alternatively an option to undo getting the previous answer as being correct
Love this script though, very useful
2 Likes
Thank you for the feedback and I am glad the script is useful for you 
Are you sure about the example ばんご・ばんごう（番号) ? Because I could not confirm this behavior for Vocabulary Reading questions - I always had to type the full hiragana answer before the auto commit is triggered.
Are you using other userscripts? They might cause an interference.
Hi Johmik, sorry for the delay but took me awhile before i came across some of the actual situations that I’ve run across
The previous example was a bad example sorry, here are some actual examples where what I’m talking about would occur:
べんじょ is correct
べんじょう typing this would incorrectly trigger true
かいぎょ is correct
かいぎょう typing this would incorrectly trigger true
Both of these examples are where the system would trigger true even though I’m part way through typing the wrong answer. Hopefully that
Thank you for the clarification, those examples make now perfectly sense. The script will immediately commit the correct entry, as it has no way to predict that the user had the intention to write more.
As you suggested, a configurable and optional delay could solve the issue with that.
I am not sure if this is worth the tradeoff, as adding a delay will delay all checks by a certain amount.
Unfortunately, my time is rather limited at the moment, so I think I won’t find time to add/experiment with this in near future.
What if you add some way for the user to signal that they’re done typing? Maybe they can hit the enter button or something when they’re done?
just kidding, I think a small debounce sound like a great suggestion
1 Like
No problem at all, the other option would be to add an option that allows the user to mark the previous answer as incorrect. Similar to what the Tsurukame ios app allows you to do.
According to ChatGPT
At an average typing speed of 40 WPM, which translates to 200 CPM (characters per minute), a typist takes 300 milliseconds between each character, so theoretically that would be a sufficient delay.
Anyway that’s just for if you ever get around to adding something like this. I might take a look at it myself 1 day.
The newest update has broken this script
2 Likes
Does anyone still work on this script? Honestly think it would be the end of WK journey without it
2 Likes
As an alternative you may have a look at Double Check lightning mode which jumps at the next item in review when you answer right.
oh thank you I will look into this now. Is it still working after the recent update?
1 Like
Sort of.
Double Check does not automatically start when you enter the reviews because of how the new dashboard is implemented. If you refresh your browser once in reviews Double Check starts and works fine thereafter.
Nice yeah got it working thank you. It’s very useful to amend typos and other functionality but unfortunately lightning mode still requires the enter button, with auto commit i can speed through much faster which is useful as i dont have much time everyday.
Nevertheless, thank you for this, it def is a help but I’m still very hopeful some hero will fix auto commit soon
2 Likes
Has someone tried refreshing the browser to start auto commit? Perhaps it is the same problem as Double Check. I don’t know. I am just asking.
yeah I have tried everything i can think (although tbf my technical knowledge is very poor) of but its not working for me unfortunately
1 Like
I just did an experiment. I turned the script off, refreshed the page, then swiped out of my browser (I’m on an Ipad and using Safari). I let my browser chill for a minute to turn off (it’s a thing I have to do on my ipad) before going back into a review. I turned the script back on. Refreshed again and went out of the review. Went back in and it’s actually working! I have checked it a few times and it’s still working! I’m assuming you’ve tried refreshing and turning it on and off but I really hope this works for you.
2 Likes
Great news! im on a Mac and at work right now, but will give this a go when i get home and update the results. Thank you for the update.
1 Like
やった! it worked, ahh im so relieved. Thank you for your help
2 Likes
I’m so glad!
2 Likes
whyyyyyy do my lifesaver scripts keep breakingggg because of the updatesssssss 
2 Likes