Even though I get an item right, I often find myself clicking on the ‘item info’ box, to reread the example sentence(s), and or my notes that I had previously left in the meaning/reading sections. Before the ‘update’, once I had finished reading, I could simply press [ENTER], then this would lead me to the next item to review. However with this new update, pressing [ENTER] close the 'item info’ box, thus I am forced to manually drag my mouse, or my keypad to the arrow ‘>’, and click to go to the next item.
I am also very much interrupted in my workflow - bearing in mind my ever growing age, I am not sure my brain will be able to adapt ![]()
My preference would be keyboard shortcuts similar to the way Bunpro offers them.
I noticed that too, that’s really a minor nuisance
I see! And no worries at all, I just wanted to make sure I understood properly. So far the last 10 button, there is actually a hotkey you can use for it (it’s labeled as Last Session Data below).
You shouldn’t need to use your mouse for anything within the review session. With the home button however, I don’t have a solution for that right now but could you perhaps explain why you open the dashboard? That might help us think of a broader solution.
As you can see from the hotkeys I shared above, you can use F or E to have a look at the more info section without needing your mouse.
If you ever forget the hotkeys, you’ll find them by clicking on the keyboard button at the bottom of the reviews page.
Let me know if I’m missing anything.
Sometimes when I make mistakes due to mixing vocabulary I want to remind myself/find out what’s the actual meaning of my wrong answer - this type of mistake usually isn’t related to, and hence goes beyond what’s included in visually similar kanji.
And the idea is that next still is Enter then?
Could you click on the item in visually similar section instead of the homepage button? That way when you open a new page, if you press the enter button accidentally, it just opens a new page instead of closing your current session
That’s correct, the Enter key is only deactivated if you use your mouse, so if you use F or any of the other hotkeys instead, you can keep pressing Enter to move to the next item
I see… I always had used my mouse to click on the info box to look within the meaning/reading sections, then pressed the Enter key to move on to the next item. Now that I understand how it gets deactivated, I suppose I will have to get used to pressing the F key instead. Thank you for the clarification.
Can it be added to the list of keyboard shortcuts?
WaniKani should continue overriding those defaults, then, as it always very helpfully did.
i would just like to come in here to say this has also been happening to me as well, i would assume it:s something to do with browser’s updating or something, i use firefox, curious if everyone else who’s had this problem is also using it, i don’t use any scripts at all atm
i will probably start to use the f key instead of my mouse from now on, thanks for pointing out that it’s a keybind
I am having the same issue. I preferred the old behaviour.
I just want to point out that the reason for the change is that some people use the tab key to navigate the page. This is a general accessibility feature of most browsers. When the tab key is used to navigate the page, a blue box will generally show around the item that is focused. When you press tab again the focus moves to the next focusable item on the page. When an item is focused, pressing enter should trigger that items default behaviour, i.e. follow a link or click the button. The issue was that if you tabbed to a link and pressed enter then you would not navigate to the links url, but instead the next review item would be loaded. This also meant if you tried to save a note while only using the keyboard, the note would not save and instead the next review item would be loaded.
The unfortunate side effect is that when you click an item with the mouse then that item is focused and remains so. I guess this is so pressing tab after clicking doesn’t take the user back to the first item on the page. I am reluctant to override this behaviour as I am sure that there are people who expect it to work this way. In general it is better not to override the browsers default behaviours as it can have unintended side effects.

