What userscripts do you have installed?
Wanikani Open Framework
WaniKani Open Framework Additional Filter
Wanikani Heatmap
WaniKani Lesson Hover Details
Wanikani: Remove Useless Panels
WKCM2
WaniKani Hide Context Sentence
Wanikani Niai Similar Kanji
Wanikani: Order Vocab’s Kanji Breakdown
WaniKani Rendaku Information
WaniKani Stroke Order
ConfusionGuesser
Wanikani Double-Check
WaniKani Pitch Info
WaniKani Show Specific SRS Level in Reviews
Wanikani Lesson Spoiler Removal
WaniKani Kanji Info
WaniKani: I Don’t know button
WaniKani Katakana For On’yomi
Wanikani Ultimate Timeline
WaniKani External Definition
Wanikani: Progress Percentages
WaniKani AI Mnemonic Images
Wanikani: Reorder Omega
Wanikani: Spread Review Intervals Display
WaniKani Keisei Phonetic-Semantic Composition
Wanikani: True Level
WaniKani - Full Progress Bar
Kanji Search Notes
WaniKani 100% Review Fanfare
Wanikani Audio [This one is custom, adds more sound effects like the burn bell]
WaniKani Item Difficulty
Wanikani: Overall Progress Bars
WK Review Item Info Level
WaniKani Review Countdown Timer
WaniKani SRS Level Progress
Wanikani Self-Study Quiz
Shin WaniKani Leech Trainer
Holy mother of god. You didn’t lie.
Thanks so much for the bug report and screenshot. From this I can tell that the issue has to do with the WanaKana open source library. I have made a couple of pull requests to that open source project which should be released shortly and I can then update WaniKani to use the version.
Extra technical info for context (for anyone who wants to know more):
The way I can tell the issue has to do with the WanaKana library is because you still have compositionend and compositionupdate events attached to the input node as well as the 2 functions still bound to the input event. The input node doesn’t have the HTML attributes that Wanakana adds nor does it have the HTML attributes that I add in Wankani so I know Wanikani has told Wanakana to unbind the input.
One of the changes I made to Wanakana was to not allow the input to be bound more than once. Perhaps one of the user scripts is calling the Wanakana bind method on the input which is binding it more than once (which seems like the case as you have 2 methods still bound to the input after unbinding). The new version of Wanakana should mean that the input can only be bound once any additional binding will be ignored.
I will post again when Wanakana is released and I have updated Wanikani.
Thanks for the technical explanation Scott, appreciate it
Not sure if this is helpful at all because it seems like you already have a good idea of what the issue is and how to fix it. But I also encountered this issue today and took a screenshot
I’m on Mac using Google Chrome, my only userscripts are
Wanikani Open Framework
Wanikani Heatmap
Jitai
Wanikani Lesson Filter
Wanikani Item Info
Hi Again,
I have released a new version about an hour ago which hopefully addresses the issue. If you encounter the issue still please do let me know. I would still like the screenshot I requested in Can't type in English for definition - #39 by tofugu-scott but could you also please provide the wanakana version by typing wanakana.VERSION in the web inspector console and reporting the version. It should be “5.1.0”
Thanks for your support so far with this issue.
Hi, @tofugu-scott , I just also ran into this issue. I have tried to comply with what you asked for in your post, but I’m not super gifted with computers, so my apologies if I messed it up.
The expansion of “input” wouldn’t scale, so I copied it out here :
function nrWrapper() {
var s, u, d, l;
try {
u = this, s = o()(arguments), d = “function” == typeof n ? n(s, u) : n || {}
} catch (t) {
f([t, “”, [s, u, a], d], e)
}
i(r + “start”, [s, u, a], d, c);
try {
return l = t.apply(u, s)
} catch (e) {
throw i(r + “err”, [s, u, e], d, c), e
} finally {
i(r + “end”, [s, u, l], d, c)
}
}
Thanks @anon3564849 for the bug report. I will continue to investigate.
Just wanted to add my findings in here, as it happens extremely frequently for me (even without userscripts):
- As far as I can tell, it only ever seems to occur after typing the reading of an item
- Running the commands from earlier also returns the wanakana version as 5.1.0 and the question type as meaning
- I’ve only tested it on Edge, which is Chromium based, but it happens often across both my laptop and desktop
- After getting through the first dozen or so reviews, it seems to not pop up anymore - no idea why
Oh, and here’s the screenshot:
I don’t think we’ve had any new reports of this issue since we’ve made the update last week, so I’ll mark this issue resolved for now. If you’re still having this issue, please email us, thanks.
Hi, I just started using Wanikani and I’m experiencing this issue. I don’t have any userscripts and clearing my cache hasn’t helped: it’ll be okay for the first exercise, then immediately swap back 
Hey eebeegames!
Shoot us an email at hello@wanikani.com with your browser and OS info (and version). Let us also know that you cleared cache and don’t use user scripts. From there, we will probably ask you to provide your web inspector console while you are experiencing the issue!
-Nick at WK