I’ve noticed during my reviews for the past few days that if I accidentally give an onyomi response when it wants kunyomi, or if I answer with the meaning when it wants the reading (or vice versa) that the input field loses focus.
As an example: With my cursor in the input field, I typed too quickly and entered “semaru” followed by the return key when it was asking for the meaning (to urge) not the reading.
It forgivingly presented me with the “Oops” message (a recent addition that I very much appreciate) but now I have to move my hands off the keyboard and use my mouse to click on the input field again before I can enter the desired answer.
I know: “first world problems” but I’d have sworn I didn’t need to do this previously. I’m pretty sure I could just hit enter to clear the “oops” message then type my response.
I’ve disabled all my scripts, but this behavior persists.
Did something change recently that might be causing this?
I had it happen to me multiple times again today, but weirdly it DID NOT lose focus twice!
I think I started hitting the backspace key pretty quickly on both occasions because I immediately realized my mistake. Maybe it’s some sort of race condition?
I can’t reproduce it though: the problem seems to manifest whenever I intentionally provide the “oops” answer no matter how quickly I start hitting backspace. Very weird.
That’s weird. I really haven’t encountered it since, so I guess you’d better contact the WK team directly and see if they got any suggestions. Good luck
I use either Safari (at home) or Opera (in my studio). Running either Mojave or High Sierra. It’s not present in either environment (any more), but there was a Safari update for Mojave around the same time, which may or may not have contributed to it working as expected.
but I’d have sworn I didn’t need to do this previously. I’m pretty sure I could just hit enter to clear the “oops” message then type my response.