Wouldn’t hurt to try. You can just delete indexeddb. Press F12 to open the dev tools, click on… I think it’s the Application tab. Look for indexeddb in the left pane, and ‘refresh’ the wkof.file_cache.
Shouldn’t it be ‘delete’? I think ‘refresh’ just updates the data displayed in the developer tools.
Last I looked (though maybe that was Firefox), there was only a refresh option. But yeah, if there’s a delete, use it.
It didn’t work for me. I deleted the indexeddb wkof cache and the browser cache for like 3 times
Open the developer tools (press F12), click on the Network tab, and see if there is an error code on the /subjects API requests.
Also, see if there are any errors in the Console tab.
I reread the last dozen posts or so. Is the problem just that the input box loses focus? And all you need to do is click in the input box to continue? (I’m not dismissing that as a problem… just making sure I understand).
If that’s the case, I think it’s solely a problem of the ‘progress’ pop-up causing the browser to de-focus the input box. I can think of two solutions:
a) @ChristopherFritz can check if the input box has focus before trying to load the /subjects data (assuming it’s this script doing that), and put the focus back on the input box after the data is loaded, or
b) In the Open Framework, I can add a way for scripts to suppress the ‘loading’ pop-up, which might come in handy for scripts on the Review screen.
Any thoughts, ChrisopherFritz?
I can definitely try it out this weekend, adding the code for this. Although more complex Javascript isn’t forte, what you propose would be simple enough to implement and see if it helps out or not.
I recognize the word being displayed, try to type the meaning or the reading but it misses a few inputs. I don’t have to click anything to regain the focus
For example: I see that the word 走る is being displayed and it is asking for the meaning. I try to type “to run” while the popup is being displayed but it just shows up “o run”. It’s not really my fault that I don’t wait for the popup to disappear because it takes a split second to appear (generally after I recognize the word and what’s been asked) and it seems to be completely random. It sometimes registers all the characters I typed while the popup is loading and sometimes doesn’t, I don’t know if it loads this way just for me, but instead of loading mid review, I think it would be better to load before starting the reviews (before the user sends the first answer) as it happens with the vocab sentences script. I wish I knew js and css to help this community, but I don’t have the time to learn it now, but I really want to put the effort to learn it
Thanks, that makes it clear to me. Sounds like the pop-up really needs to be disabled.
@ChristopherFritz, I think you can simply do this before you load the data:
var original_progress_function = wkof.Progress.update;
// A function that does nothing.
wkof.Progress.update = function () {};
And, optionally, restore it after you’re done loading:
wkof.Progress.update = original_progress_function;
Alongside adding that, I do have a question about this line in my code:
wkof.ItemData.get_items(item_config).then(process_items);
This gets called every time a new word comes up for review. Does it cache results? Or should I call get_items only once, then cache the results in a variable to use for subsequent reviews?
It does cache the server results, but I think it still has to parse the huge cache object each time you call that, so just keep the processed result in a variable instead.
This is a really interesting script! It reminds me of the back of my kanji flash cards, where I can only see the vocabulary if I flip it over. I hate my vocabulary card method and that’s why I’m on WK. Maybe I would like them more if the vocabulary words were on the front. It never occured to me.
I was on the fence about seeing them up front, but I don’t see it as a double edged sword as other persons have noted. Instead of a double edge sword, I see this as training wheels: Some parents are extremely against the idea of training wheels on bikes because they believe it makes riding without them harder, so they make the kid have a more brutal up front experience which for some can be short lived and over soon. I don’t think that’s the case for Kanji. It is not a short lived tough time, it is a prolonged agony.
I’m going to try these training wheels! Do I want to struggle with vocabulary less as a beginner? No, I want to be functionally reading as fast as possible. I think pushing fine-tune kanji recommendation last is a very interesting idea.
Is there a way to make the polling/caching window pop-up completely invisible? I find the little pop-up a little jarring. I’m guessing that it’s probably some default thing about Framework, I’ve seen other plugins use it. I want to right click and hide it with inspector css or adblock but it’s too damn fast ![]()
It’s part of the framework. It appears if a query takes longer than 2sec, which was relatively rare when I first wrote the framework. Now, I think queries have gotten slower. I need to make that delay longer. But also, I can add an override somewhere, so users can disable it permanently and scripters can disable it on a query-by-query basis…
Maybe caching less words would do the trick? In my case, only want to see less than 5 words max as I’m frequently using a small tablet (lenovo duet 13")
Either way, thanks for your hard work on this. It’s made reviews much more enjoyable for me as I push myself to try to read all the words and look up the ones I don’t know yet
This was SO helpful. Just dropping in to say thank you!
hi
could you please fix and update this script? now it gets stuck with this loading pop up when this script is active
when not activated, the pop up window appears and reloads normally and disappears, this is the only script this is happening on firefox.
What is the name of the extension you are using for Firefox? I want to see if I can replicate the issue.
The odd thing is that the WaniKani Kanji Review Vocabulary List should not be active on the WaniKani home page. It should only be active on review sessions:

Does your copy of the script have this @match line?



